Thanks, I looked at the description from the -1 build, attempting to toggle bluetooth off from the GNOME quick settings reliably pegs it at 100%. I have to killall -9 bluetoothd to recover.
That happens with both this and the upstream tip+patch build I referenced earlier BTW.
This update has been submitted for testing by pbrobinson.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted bluez-5.73-1.fc39, and has inherited its bugs and notes.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works.
Looks like the slow-scroll issue may not be fixed, testing now.
https://github.com/bluez/bluez/issues/778#issuecomment-2005841484
It's at least greatly improved.
I can still reproduce with this build :(
https://github.com/bluez/bluez/issues/778#issuecomment-2007507985
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Also noticed that when this slow-scroll-on-wakeup happens restarting bluetooth.service (to work around it) hangs for a long time before completing.
This update can be pushed to stable now if the maintainer wishes
ok here
Still reproducible by me and others, see same upstream issue.
I tried adding this change to a local
fedpkg mockbuildbut the patch wouldn't apply. I'll try to find time to get it built with that tomorrow.bluetoothd still hanging, but with 100% CPU usage now :)
I have a crude workaround for the slow-scroll issue. Works with this build in addition to tip+patch as described there.
I haven't encountered
bluetoothdpegging the CPU - @decathorpe any steps to reproduce that?FWIW leaving my karma at -1 for now until I've had more time to shake this down.
Not sure how to reproduce it, but it coincided with bluetoothd becoming unresponsive.
Thanks, I looked at the description from the -1 build, attempting to toggle bluetooth off from the GNOME quick settings reliably pegs it at 100%. I have to
killall -9 bluetoothdto recover.That happens with both this and the upstream tip+patch build I referenced earlier BTW.
100% CPU at
rfkill blockupstream at https://github.com/bluez/bluez/issues/785my bluetooth mouse works fine
This update has been obsoleted by bluez-5.73-3.fc39.