bluetoothd unable to establish connection after resume from suspend
Bug #1773912 reported by
Alexander Lochmann
This bug report is a duplicate of:
Bug #1759628: bluez regression: Bluetooth audio fails to reconnect after resume .
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 18.04 LTS
Release: 18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://
100 /var/lib/
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily connect my BT headset.
To post a comment you must log in.
Kernel Version: 4.16.5
I also tried 'rfkill block bluetooth' and 'rfkill unblock bluetooth' after resume, but no success.