This continues to be a problem with Plasma 6, even now with the upgrade to 6.0.5.
A bug report has been filed and updated: 1223405 – Bluetooth disabled at each login since upgrade to Plasma 6, however there have been no other comments to it, aside from mine.
The slowroll tag was not available for this post, but this also occurs with Slowroll.
This does not happen to me. My device is currently asking after my Qudelix-5K.
What baffles me is that your device used to work. If it had never worked I would ask if you had problematic hardware or were missing a driver.
This problem started with the upgrade to Plasma 6.
Under Plasma 5, Bluetooth was enabled at each and every bootup. It was perfect.
And on a separate TW install with the XFCE desktop (on thumb drive connected to the same physical hardware), Bluetooth also comes up each and every time.
The primary difference between you and me seems to be that you upgraded from Plasma 5. I would assume the upgrade messed up something in bluedevil, given that Bluetooth works everywhere except KDE. Can you see if deleting bluedevilglobalrc in ~/.config fixes your problems? That seems to be what fixed a similar problem in Plasma 5, but if it doesn’t work you may have to thoroughly reinstall bluedevil.
Removing that file from ~/.config, did not work. The Plasma 6 package is ‘bluedevil6’. Upon removal and reinstall of this package, the problem remains.
The Bluetooth dongle has a blue light on it that lights up when it is connected. After login, the light comes on for 1 second during the process, then goes out. So it would seem that something during the login process is correctly enabling BT, but incorrectly disabling it a second later.
At this point, I’m going to look at other options. Thanks for the replies.
The Bluetooth setting is to ENABLE Bluetooth at login. Reinstalling the package didn’t fix this, neither did the removal of that rc file.
Weird. I don’t really know what to say, other than good luck and maybe see if a new user account has the same problems. If you just decide to try another DE, try to think of this as a good chance to seriously look at other desktop environments. Either you’ll find another DE that suits you better, or you’ll find out that KDE really is the best for you, at which point you should copy your home folder off your drive and reinstall using a newer snapshot.
I found a KDE bug report on this 487063 – Bluetooth gets turned off after login, even with "On login: Enable Bluetooth", was opened last month and until I added a comment earlier that the issue is also present in both openSUSE Tumbleweed and Slowroll, there were no additional comments since the bug report was filed.
My personal experience when it comes to submitting bug reports, with very few exceptions, has been extremely negative. I submitted a bug report to Thunderbird, which had to be close to 15 years ago by now. No action was ever taken to resolve it, no comments from anyone else. The last time I tried Thunderbird a few years ago, the bug was still present. So I eventually closed it with a note that there were no responses from the developers after all that time. And that was the last time I used Thunderbird.
I tried installing XFCE on the same hardware and had trouble. None of the KDE-created desktop launchers would work, they all had locks embedded into the icons and when I renamed the Desktop directory to something else, then logged in new with XFCE, a new Desktop directory was not created. Then back to KDE and all of the folders inside the home directory, now had desktop entries. I was able to remove XFCE completely and fixed the KDE Desktop default, which removed all of the extra entries. So it sounds like a second DE cannot be installed on the same hardware, without having any issues occur. My preference is not to have to reinstall openSUSE.
Bug report submitted. 1226062 – Bluetooth not enabled after KDE Plasma 6 login - unexpected NULL in bluetooth.service
There is an unexpected NULL in the journal output, when checking the status of bluetooth.service.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.