[regression] bluetooth headset not connecting after regular update

Bug #1701572 reported by Thomas Mayer
6
This bug affects 1 person
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-mainloop-glib0 1:8.0-0ubuntu3.3
 pulseaudio 1:8.0-0ubuntu3.3
 pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
 pulseaudio-module-gconf 1:8.0-0ubuntu3.3
 pulseaudio-module-x11 1:8.0-0ubuntu3.3
 pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
 pulseaudio-utils 1:8.0-0ubuntu3.3

 linux-generic-hwe-16.04 4.8.0.58.29
 linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
 linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
 linux-headers-generic-hwe-16.04 4.8.0.58.29
 linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
 linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
 linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
 linux-image-generic-hwe-16.04 4.8.0.58.29
 linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
 linux-tools-generic-hwe-16.04 4.8.0.58.29

For pulseaudio changes, I got this changelog:

--- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 pulseaudio-module-zeroconf pulseaudio-utils) ---
Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog [216 kB]
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-Add-support-for-automatic-switch-between-h.patch
    - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
    - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
      . 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-policy-do-A2DP-profile-restoring-a-bit-lat.patch
      . 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-add-new-card-profile-hook.patch
      . Backport from upstream (commit 7b6260140149) to allow for correct
        profile selection.
    - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
      . 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
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
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
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet splash vt.handoff=7
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.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
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

Revision history for this message
Thomas Mayer (thomas303) wrote :
Revision history for this message
Thomas Mayer (thomas303) wrote :

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
AutoEnable=true
in /etc/bluetooth/main.conf
does not fix this issue

Revision history for this message
Thomas Mayer (thomas303) wrote :

I worked around it.

I had to remove --purge
bluetooth bluez blueman bluetooth pulseaudio pulseaudio-module-bluetooth

Then I removed all pairing information with devices, both in ~/.config/pulse and /var/lib/bluetooth

Then rebooted

Then paired my A2DP device again, this time with blueman.

Then everything was working.

I think the main problem here is that I once had device discovery disabled in /etc/pulse/default.pa. But that's not a bug in ubuntu.

Issue can be closed.

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

Other bug subscribers

Remote bug watches

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