Comment 47 for bug 1759628

I confirm

Bug is fixed. All working fine. automatic reconnect without turning on/off
on my headphones.

On Thu, Jul 5, 2018 at 10:11 AM Alexander Lochmann <
<email address hidden>> wrote:

> I downloaded and installed bluez_5.48-0ubuntu3.1_amd64.deb. It seems that
> the bug is fixed. :)
> Thx!
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1778506).
> https://bugs.launchpad.net/bugs/1759628
>
> Title:
> bluez regression: Bluetooth audio fails to reconnect after resume
>
> Status in bluez package in Ubuntu:
> Fix Released
> Status in bluez source package in Bionic:
> Fix Committed
> Status in bluez package in Fedora:
> Fix Released
> Status in Suse:
> Fix Released
>
> Bug description:
> [Impact]
>
> Users of Bluetooth audio have no sound after they suspend and resume
> the system.
>
> [Test Case]
>
> 1. Connect to Bluetooth audio device
> 2. Suspend & Resume
> 3. Reconnect to Bluetooth device.
>
> [Regression Potential]
>
> Low. Although common Bluetooth code is modified in the fix, it has
> been released as a patch in other distros for some time already.
>
> [Other Info]
>
> Already released to cosmic as part of bluez version 5.50.
>
> This regression in bluez 5.48 has already been identified and fixed
> upstream. Report is here <https://marc.info/?l=linux-
> bluetooth&m=151616078627045&w=2> and patch is here
> <
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=d6e9539e31c6bb5afd39ec6f09c518d232e6345d
> >.
>
> Syslog reports messages as follows when this issue is happening (I have
> replaced my device's MAC address with [MAC]):
> Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c:
> Information about device /org/bluez/hci0/dev_[MAC] is invalid
> Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error:
> org.bluez.Error.InvalidArguments
> Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c:
> Information about device /org/bluez/hci0/dev_[MAC] is invalid
> Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error:
> org.bluez.Error.InvalidArguments
>
> Workaround is to run sudo systemctl restart bluetooth after resume.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: bluez 5.48-0ubuntu3
> ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
> Uname: Linux 4.15.0-12-generic x86_64
> ApportVersion: 2.20.9-0ubuntu1
> Architecture: amd64
> CurrentDesktop: KDE
> Date: Wed Mar 28 12:37:11 2018
> InstallationDate: Installed on 2018-03-23 (5 days ago)
> InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180306.1)
> InterestingModules: rfcomm bnep btusb bluetooth
> MachineType: Hewlett-Packard HP ProBook 640 G1
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic
> root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
> SourcePackage: bluez
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 01/25/2018
> dmi.bios.vendor: Hewlett-Packard
> dmi.bios.version: L78 Ver. 01.43
> dmi.board.name: 2101
> dmi.board.vendor: Hewlett-Packard
> dmi.board.version: KBC Version 16.3C
> dmi.chassis.type: 10
> dmi.chassis.vendor: Hewlett-Packard
> dmi.modalias:
> dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
> dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
> dmi.product.name: HP ProBook 640 G1
> dmi.product.version: A3009DD10303
> dmi.sys.vendor: Hewlett-Packard
> hciconfig:
> hci0: Type: Primary Bus: USB
> BD Address: 80:00:0B:C7:4D:1C ACL MTU: 310:10 SCO MTU: 64:8
> UP RUNNING PSCAN
> RX bytes:5025 acl:32 sco:0 events:202 errors:0
> TX bytes:5785 acl:32 sco:0 commands:103 errors:0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions
>