New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another suspend/resume issue #284
Comments
It might well be related somehow, but I tried building a fresh bluez package from the latest github (with the adapter: Remove custom MGMT send/reply timeout patch), and the issue remains. |
Also upgraded kernel to 5.15.19 where this patch was added (same in 5.16.5): That didn't solve the issue, same crash after suspend/resume. This with bluez-5.63 built from today's github, so the changes mentioned in #275 does not solve this issue either. As already mentioned, bluez-5.62 works perfectly. |
@hamkg looks like it is related to: |
This makes InterfacesAdded respect the object hierarchy in case its parent has pending interfaces to be added. Fixes: bluez#284
This makes InterfacesAdded respect the object hierarchy in case its parent has pending interfaces to be added. Fixes: bluez#284
Thanks! I rebuilt bluez-5.63 with the patch applied and can confirm that bluez now works as it should after suspend/resume. |
This makes InterfacesAdded respect the object hierarchy in case its parent has pending interfaces to be added. Fixes: bluez#284
This makes InterfacesAdded respect the object hierarchy in case its parent has pending interfaces to be added. Fixes: bluez#272 Fixes: bluez#284 Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1534857 Fixes: https://bugs.archlinux.org/task/57464
This makes InterfacesAdded respect the object hierarchy in case its parent has pending interfaces to be added. Fixes: bluez#272 Fixes: bluez#284 Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1534857 Fixes: https://bugs.archlinux.org/task/57464
This makes InterfacesAdded respect the object hierarchy in case its parent has pending interfaces to be added. Fixes: bluez/bluez#272 Fixes: bluez/bluez#284 Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1534857 Fixes: https://bugs.archlinux.org/task/57464
Slackware64-current, Linux kernel 5.15.18, Bluez-5.63, blueman-2.2.3, pulseaudio-15.0
While my bt headset connects properly directly after booting it won't work after suspend/resume. It connects, drops, connects again and so on. If I try to connect manually, the blueman applet disappears with the following message:
"Connection to BlueZ failed
Bluez daemon is not running, blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started."
Restarting with sh /etc/rc.d/rc.bluetooth restart does not help, same behaviour.
In /var/log/syslog I find:
I've seen other reported issues concerning suspend/resume and in #282 it was mentioned that this might be fixed in kernel 5.16, not yet in the Slackware repo. If I find the time I might try to build 5.16.5 and see what happens. Till then, Bluez-5.62 works just fine.
The text was updated successfully, but these errors were encountered: