STEPS TO REPRODUCE In "System settings" configure the Bluetooth adaptor to be disabled at login. Then start a new Plasma session. OBSERVED RESULT Bluetooth is active. EXPECTED RESULT Bluetooth should be inactive. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-gentoo (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics
Works for me. Does the issue reproduce in a new user account on the same machine? Did this work in the past and break recently? When it broke, was there also a kernel update?
(In reply to Nate Graham from comment #1) > Did this work in the past and break recently? Yes, it broke when I upgraded to Plasma 6.0.90. > When it broke, was there also a kernel update? Yes, there was. If it helps, after logging out and then back (restarting the Plasma session), the issue doesn't reproduce, BUT if I reboot the issue is pops up again, even after upgrading to 6.1.0.
Can you paste the contents of your ~/.config/bluedevilglobalrc file before logging out, and after logging in? Unless they're identical, of course; in that case, paste it once. :)
(In reply to Nate Graham from comment #3) > Can you paste the contents of your ~/.config/bluedevilglobalrc file before > logging out, and after logging in? Unless they're identical, of course; in > that case, paste it once. :) Before reboot: [Adapters] 80:30:49:72:A7:5E_powered=false [Devices] connectedDevices= [Global] launchState=disable After reboot: [Adapters] 80:30:49:72:A7:5E_powered=true [Devices] connectedDevices= [Global] launchState=disable
I don't know what turns the "80:30:49:72:A7:5E_powered" property to false. I manually disabled Bluetooth after reboot, but the file contents didn't change.
*** Bug 487063 has been marked as a duplicate of this bug. ***
Can not reproduce on Arch Linux. The Framework laptop 16 boots up with a powered off Bluetooth adapter and (according to rfkill) with a soft-blocked Bluetooth in general. The content of the config file does not change. Looking at your kernel version, it seems you are using Gentoo. I know Gentoo is a DIY distro, so are you sure this is not some kind of a local setup issue? Is there any chance you could test it with a different distro on the same hardware? Also, what is the state of `rfkill` and `bluetoothctl show <Tab to autocomplete your-controller>` before and after the reboot?
Looking at bug 487063, I'd say the main suspect is the kernel line (6.9), not the distribution (which is the only distribution at hand). Before reboot: > rfkill --output-all list 6 6: hci0: Bluetooth Soft blocked: no Hard blocked: no > bluetoothctl show Controller *** (public) Manufacturer: 0x001d (29) Version: 0x08 (8) Name: BlueZ 5.76 Alias: *** Class: 0x00000000 (0) Powered: no PowerState: off Discoverable: no DiscoverableTimeout: 0x000000b4 (180) Pairable: yes ... After reboot: > rfkill --output-all list 0 0: hci0: Bluetooth Soft blocked: no Hard blocked: no > bluetoothctl show Controller *** (public) Manufacturer: 0x001d (29) Version: 0x08 (8) Name: BlueZ 5.76 Alias: *** Class: 0x007c0000 (8126464) Powered: yes PowerState: on Discoverable: no ... Configuration says Bluetooth should be inactive at login. If I suspend and then resume, Bluetooth remains inactive, as configured.
Assuming that nobody touched the Bloutooth related code in the meantime, well, what do you know?! I upgraded to kernel 6.10.11 and the bug is gone.