SUMMARY When turning on a laptop with paired bluetooth keyboard and mouse, the devices connect when it reaches the login screen, and I can type and click. After logging in however, the bluetooth tray icon is missing, and bluetooth is disabled. I have to manually turn it on again. This seems to apply regardless of the setting "On login: Enable Bluetooth" STEPS TO REPRODUCE 1. In System Settings > Bluetooth > Settings/Configure, set "On login" to "Enable Bluetooth" 2. Reboot (might need cold reboot) 3. After login, check if bluetooth is enabled OBSERVED RESULT After login, bluetooth is disabled EXPECTED RESULT Bluetooth being enabled after login SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-arch1-2 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION The bug is a bit flaky. Sometimes bluetooth gets enabled, other times it doesn't. I'll gladly supply logs if someone tells me how. This might have some connection to Bug 457130 or Bug 429519
Same occurring on openSUSE Tumbleweed and openSUSE Slowroll, began when KDE Plasma was upgraded from 5 to 6.
My Bluetooth dongle has a blue light on it, that comes on when it's connected/enabled. During the KDE login process (either X11 or Wayland), the light on the dongle comes on, then one second later, goes out and Bluetooth comes up disabled, each time. Something during the login process, is enabling then disabling Bluetooth. I changed the 'powered' entry in ~/.config/bluedevilgloabalrc from =false to =true. On a reboot, the login process also changes that entry back to =false, with Bluetooth continuing to come up disabled.
Another suggestion I tried, was to comment out the entries under [Adapters] in bluedevilglobalrc. Upon the next login, I found the # tag was automatically removed from the file during the login process. Something seems to be overriding or changing the bluedevilglobalrc file to cause Bluetooth to come up disabled.
After trying many things, it would appear that something in KDE 6, if not bluedevil6 itself, is changing the bluedevilglobalrc config file at each login/bootup, causing Bluetooth not to be enabled. The developers really need to have a look at this.
I can confirm this behavior. My system: Operating System: openSUSE Tumbleweed 20240612 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Aspire A515-44 System Version: V1.12 Output systemctl: sebastian@acer-aspire:~> systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled) Active: active (running) since Sun 2024-06-16 12:52:53 CEST; 24s ago Docs: man:bluetoothd(8) Main PID: 1077 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CPU: 37ms CGroup: /system.slice/bluetooth.service └─1077 /usr/libexec/bluetooth/bluetoothd That's weird, Bluetooth is "enabled" and "active"; however, the KDE applet shows Bluetooth as non-active at every boot, and Bluetooth is not working.
*** This bug has been marked as a duplicate of bug 488652 ***