bluetoothd unable to establish connection after resume from suspend

[Alexander Lochmann]

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.

[Alexander Lochmann (alexander-lochmann)]

Kernel Version: 4.16.5
I also tried 'rfkill block bluetooth' and 'rfkill unblock bluetooth' after resume, but no success.

[Daniel van Vugt (vanvugt)]

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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.