*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773912
Title:
bluetoothd unable to establish connection after resume from suspend
Status in bluez package in Ubuntu:
Confirmed
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://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
