Ok, I've found the problem, and reverting this one small change allows
all the bluetooth audio hardware I have here to connect and work.

For those following along with the technical side, I reverted/removed
one hunk from 0502-bluetooth-bluez5-bring-back-SCO-over-PCM-

@@ -1582,7 +1738,8 @@ static void stop_thread(struct userdata *u) {
     if (u->transport) {
-        u->transport = NULL;
+        /* Do not set transport pointer to NULL. When failing to switch
+         * profile NULL u->transport would assert. */
     if (u->sink) {

I can only summise that this was relevant for vivid, but work on pulse's
bluez5 module between pulse in Vivid and pulse in Xenial improved this

As such, I've uploaded a new revision of pulseaudio to my PPA for
Xenial, ppa:themuso/ppa, with this hunk reverted.

Could everybody affected by *this* bug on Xenial please add my PPA,
update to pulseaudio in my Xenial PPA and report back and let me know
whether things are working for you.


You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.

  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:      16.04

  Pulseaudio Version:

    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
          500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
          100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
   UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
   UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
   UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
   UUID: Unknown                   (000080ff-0000-1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to