SUMMARY After bluetooth service has been disabled in background services (and showing as Not running on that interface) under System Settings, it still shows up on system tray active and even after reboot. STEPS TO REPRODUCE Go to System Settings -> Startup and Shutdown -> Background Services, and uncheck Bluetooth. OBSERVED RESULT After restart it still shows up in the system tray. EXPECTED RESULT It should be disabled not appearing on the system tray. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 5.20 (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION
I can confirm this intermittently. Sometimes shutting down the machine with bluetooth disabled causes it to be re-enabled on boot.
*** Bug 435885 has been marked as a duplicate of this bug. ***
Disabling system services via Background Services KCM is not supported and may break your system or cause various weird behavior, which is why the whole Background Services KCM was recently hidden from the System Settings sidebar to prevent users from breaking their OS. Besides, the service that can be disabled there is not the whole Bluetooth stack; it's just a thing that prompts you where to save incoming files, how to pair new devices and other integration stuff like that. If you disable that "kded" module, you'd just lose that integration. Kernel drivers and BlueZ stack would still be running and functional, adapters and devices would remain operational, and libraries will be able to access them. If you want to disable your whole Bluetooth stack at login, you should go to the System Settings -> Bluetooth, Enable (if it is disabled, otherwise the following UI won't show up), tap Configure, and on that configuration page select "On login:" "Disable Bluetooth" option.
ratijas, the other dupilicate bug report and that's how I've had experienced (need to check again if the bug still occurs), is about disabling Bluetooth with the slider checkbox in the applet. Should the other than be re-opened?
I closed the other one with a different reasoning. Why would you want to reopen it?
(In reply to ratijas from comment #5) > I closed the other one with a different reasoning. Why would you want to > reopen it? You closed the other bug with the different reasoning literally 3 seconds before I posted my question. :) So, never mind!