Created attachment 166648 [details] Current configuration. SUMMARY “Restore previous status” doesn't enable Bluetooth at boot, despite Bluetooth not being manually disabled by the user before previous shutdown. STEPS TO REPRODUCE 1. Invoke `kcmshell5 kcm_bluetooth`. 1. Choose “Configure”. 1. Enable Bluetooth, if necessary. 1. Choose “Restore previous status”. 1. Invoke `systemctl reboot`. 1. Log in. OBSERVED RESULT Login does not automatically enable Bluetooth. EXPECTED RESULT Bluetooth should be enabled at login. SOFTWARE/OS VERSIONS Operating System: cpe:/o:opensuse:tumbleweed:20240306 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION * Originally mentioned at https://forums.opensuse.org/t/bluetooth-no-longer-starting-at-boot/169758/11. * Although https://bugs.kde.org/describecomponents.cgi?product=Bluedevil lists https://bugs.kde.org/buglist.cgi?product=Bluedevil&component=kcm&resolution=---, https://bugs.kde.org/enter_bug.cgi?product=Bluedevil&component=kcm doesn't appear to allow me to choose that component.
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #0) This occurred a few OS updates ago. I wish I knew which update caused it. Apologies.
At this point I'm willing to bet that you've made some customization to your OS that caused this to happen without realizing it. :) Does it happen in a new clean user account? if not, then my suspicion is correct.
(In reply to Nate Graham from comment #2) Why do you assume that? I'm not one to customize my OS much, and I've certainly not ever messed with Bluetooth (it being the complex and fragile standard that it is). Considering I've been using the same system for about a year, and this is a rolling release OS, I'm not surprised small things will break occasionally. Are you? Regardless, your estimation is correct that it works on a new user (and another one which I've had for a while but haven't used for some time). Any ideas of what I should check to ascertain what's been changed for my account? I certainly didn't change anything on the day it broke, but *did* update, so I can't think of how I might have caused this.
Created attachment 167490 [details] Plasmoid GUI if forcefully enabled at boot regardless of previous boot's configuration. Noteworthily, after updating to https://kde.org/info/plasma-6.0.1/, I've a useful demonstration — should I instruct it to enable it at boot regardless of the preference recorded during previous OS deinitialization, it enables as expected, but the GUI does not appear to indicate this. See the attachment — it certainly shouldn't be able to list available devices if disabled.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Forgot to change the bug status after remediating the NEEDSINFO, but it isn't present in my new installation anyway, so I'll resolve this.
Created attachment 168521 [details] Plasmoid GUI after reinstatement from sleep. It's just occurred to me again, this time on cpe:/o:fedoraproject:fedora:40, but after restoring the OS from sleep. It's like https://bugs.kde.org/attachment.cgi?id=167490&action=edit.
Created attachment 168522 [details] Plasmoid GUI after attempting to re-enable it (after sleep). (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #7) When I attempted to re-enable it, it then acted as if it was disabled (consequently implying that it was enabled previously, but that merely the toggle is not reflecting its state).
Created attachment 168523 [details] Plasmoid GUI after trying 2 times to re-enable it. (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #8) It displaying correctly after two clicks on the toggle appears to confirm this.
Happened again in Fedora. Forgot previously to set it as REPORTED when I re-experienced it.
*** This bug has been marked as a duplicate of bug 469119 ***
(In reply to Nate Graham from comment #2) Seems like it might not have been my fault after all. :>