[regression] bluetooth headset not connecting after regular update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi, my bluetooth headset Arctic P311 was connecting until I installed these updates:
libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-
pulseaudio-
pulseaudio-
pulseaudio-
pulseaudio-utils 1:8.0-0ubuntu3.3
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
For pulseaudio changes, I got this changelog:
--- Änderungen für pulseaudio (libpulsedsp libpulse-
Holen:1 http://
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium
[Luke Yelavich, Konrad Zapałowicz]
* Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
where users would experience some combination of:
- Bluetooth headset/speakers listed but not selectable in Sound settings
(LP: #1283003)
- [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
mode) (LP: #1438510)
- [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
to HSP/HFP first (LP: #1582213)
* Specific patches from upstream used to address the above problems:
- 0103-bluetooth-
- 0104-bluetooth-
- 0106-bluetooth-
. Backport from upstream to fix a bug in Xenial where an incorrect
audio profile is applied for a headset connected over Bluetooth
making using it impossible.
- 0105-bluetooth-
. Fix a crash that happens if the BT headset is the only non-monitor
source in the system and the last "phone" stream dies.
- 0700-pulsecore-
. Backport from upstream (commit 7b6260140149) to allow for correct
profile selection.
- 0701-bluetooth-
. Backport from upstream waiting for all profiles to connect before
creating a card.
Before, the P311 headset was connecting, after the update, it's not. Looks like a regression.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluetooth 5.37-0ubuntu5
ProcVersionSign
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 30 16:06:36 2017
InstallationDate: Installed on 2014-11-29 (944 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E5510
PackageArchitec
ProcEnviron:
LANGUAGE=de_DE
TERM=xterm-
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E5510
dmi.product.
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 5C:AC:4C:F8:E1:98 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:2055 acl:26 sco:0 events:96 errors:0
TX bytes:3977 acl:28 sco:0 commands:62 errors:0
Changed in bluez (Ubuntu): | |
status: | New → Invalid |
When I try to connect the headset (which still seems to pair), I see the little lock next to the bluetooth device for ~0.5 seconds. Then the lock disappears.
Syslog reports:
Jun 30 16:00:40 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for 00:1A:7D:70:08:7E: Protocol not available
Jun 30 16:00:45 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for 00:1A:7D:D0:24:5D: Protocol not available
Enabling the line main.conf
AutoEnable=true
in /etc/bluetooth/
does not fix this issue