ROSA QA denied libbluedevil and bluedevil 2.0rc1 -> 2.0 update because of regression: ------------------------------------------------------------------------- I have a bluetooth sound system. The system automatically enabled after reboot by old version. With new version after reboot I must 1) Enable bluetooth in tray 2) Enable the sound system in tray menu It's big regression (for bluetooth mouse too!) ****************************************** QA Denied ------------------------------------------------------------------------- Reproducible: Always
So it looks like this commit https://projects.kde.org/projects/playground/libs/libbluedevil/repository/revisions/c76d6e50ba6466403457371ab8416b0600af4a77 fixed issue with adapters being powered on startup even if user powered them off before. But it also introduced new issue, as you are experiencing, that some adapters would be always off on startup. I will try to fix it by saving the powered state for all adapters and restoring it on startup. I hope I will have patch ready in few days (I'm busy right now). After this fix, I will release new version 2.0.1
Created attachment 89952 [details] Save and restore adapters state in kded module Can you please try this patch?
Fixed with this commit: http://quickgit.kde.org/?p=bluedevil.git&a=commit&h=ff6ae6022286e118e98efd69ba1833f2be2e4842
(lib)bludevil 2.1 on arch linux. bluetooth adapter BCM2045 (0a5c:2101) I still need to enable the adapter (which is correctly recognized though) everytime I resume from suspension to ram. Am I missing something or is the adapter supposed to be automatically enabled?
The adapter powered state should be restored after resuming from suspend. This feature in Bludevil KDED module currently depends on logind.
I know this is not a support forum, but can you help me understand where to check for errors on my system/check why automatic enabling is not working?