[Touch-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** 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
[Touch-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1759628, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 1759628
bluez regression: Bluetooth audio fails to reconnect after resume
--
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:
New
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
[Touch-packages] [Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Kernel Version: 4.16.5
I also tried 'rfkill block bluetooth' and 'rfkill unblock bluetooth' after
resume, but no success.
--
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:
New
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
