Bluetooth doesn't reconnect to my headsetup post resume from sleep

Bug #1763156 reported by Anmar Oueja
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned

Bug Description

Steps to repro:

* Cold boot the laptop
* Pair it with bluetooth headset
* Listen to music
* Turn off the headset or turn off the bluetooth on the laptop
* Play music, sound comes out of the laptop speakers
* Turn on the headset back on or the bluetooth on the laptop
* Headset reconnects with the laptop and audio plays from the headset

-- all the above is expected --

* Suspend the laptop
* wait a minute or two for the headset to power down
* Resume the laptop
* Turn on the bluetooth headeset
* It doesn't automatically reconnect to the laptop (not expected behaviour)
* Launch Gnome Settings and select Bluetooth and force the headset to connect
* It connects for 2 seconds then disconnects (not expected behaviour)

The only to get the headset to reconnect again is by restarting the bluetooth.service using systemctl.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 11 15:28:28 2018
InstallationDate: Installed on 2018-04-03 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc.
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash nouveau.modeset=0 vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0JHP5H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: F8:34:41:D4:8F:36 ACL MTU: 1021:4 SCO MTU: 96:6
  UP RUNNING PSCAN ISCAN
  RX bytes:19284 acl:106 sco:0 events:2607 errors:0
  TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

Revision history for this message
Anmar Oueja (anmar) wrote :
Revision history for this message
Anmar Oueja (anmar) wrote :

Problem seems resolved with bluez 5.48.2 as outlined in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1534857#c30

Revision history for this message
Anmar Oueja (anmar) wrote :

The following patches were added to the 5.48 version in Fedora and they did fix the problem. Perhaps worth you adding them as well. Please see https://koji.fedoraproject.org/koji/buildinfo?buildID=1040106 and the bug https://bugzilla.redhat.com/show_bug.cgi?id=1534857

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bluez (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.