Bluetooth headset/speakers listed but not selectable in Sound settings

I am having the same problem with the Bose Soundlink III worked (mostly fine) until Friday evening updates (02-28-2014), .

In fact, if I enable bluetooth from the setting dialog it immediately stops after enabling. If I hardware disable bluetooth, then turn it back on I can then try and pair the device, but nothing is ever found. I did see some bluetooth and pulse audio updates come down the pike, but no idea what is causing this problem

If there is any information I could provide that would be helpful please let me know.
Lenovo T61P
Ubuntu 14.04 - 3.13.0-10-generic

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

same here. while trying to pair a new device no device is found

dell latitude e6510. Ubuntu 14.04 - all updates installed

Same problem for me. No devices found. Until and including Ubuntu 13.10 no problems with bluetooth audio.

Of course, hardware key for WiFi and Bluetooth is activated.

State "On" and "Off" in Unity Bluetooth menu and Bluetooth dialog seem to be not in sync. If I change one of them, the change is not reflected in the other. Perhaps switching to "On" does not work in both places?

HP 635, Ubuntu 14.04, all updates installed.

My symptoms match the above, but most importantly, booting from a daily trusty image, Bluetooth works perfectly, while on the desktop it stopped working after the upgrade.

I have the above issue also. Running 14.04. Bluetooth worked fine prior to the upgrade from 12.04.

I do note that during the update, I noticed that my bluetooth failed. I was putzing around on the web while the updater was running and my mouse eventually failed to move. I believe it was when it was adding packages.

I am also encountering the Bluetooth menu and dialog box not being synced together.

Has a workaround been found at this time?

Similar situation.
Lubuntu 14.04
The headset is paired, the profile is connected. Device for sound output does not appear.

Same here, with an Apple wireless keyboard. The keyboard wasn't working so I tried to remove and readd it but my computer can't find it. My nexus 4 finds the keyboard in a second.

Hi, I have the same problem with two different bluetooth a2dp devices, maybe this could be useful:

E: [pulseaudio] bluetooth-util.c: org.bluez.Media.RegisterEndpoint() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "RegisterEndpoint" with signature "oa{sv}" on interface "org.bluez.Media" doesn't exist
E: [pulseaudio] bluetooth-util.c: org.bluez.Media.RegisterEndpoint() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "RegisterEndpoint" with signature "oa{sv}" on interface "org.bluez.Media" doesn't exist
E: [pulseaudio] bluetooth-util.c: org.bluez.Media.RegisterEndpoint() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "RegisterEndpoint" with signature "oa{sv}" on interface "org.bluez.Media" doesn't exist
E: [pulseaudio] bluetooth-util.c: org.bluez.Media.RegisterEndpoint() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "RegisterEndpoint" with signature "oa{sv}" on interface "org.bluez.Media" doesn't exist
E: [pulseaudio] bluetooth-util.c: Volume change does not have an associated transport
E: [pulseaudio] bluetooth-util.c: Volume change does not have an associated transpor

Also affects me but if I use Veromix to force the output device it works until I open the sound settings again and it changes the output device back always.

Upgraded to 14.04. Apple bluetooth keyboard stops working after login. Strangely works only during login where I can enter the password after the keyboard auto connects. Bluetooth mouse works fine though. See a lock symbol on the Bluetooth tray icon.

After upgrade from Ubuntu 12.04 LTS to Ubuntu 14.04 LTS (32 bit version) for my LG F1 Express Dual, I cannot get reliable A2DP working on my Bluetooth Headset - Model is Philips SHB4000. The old trick of using Blueman / Refresh Services and then re-connect no longer works. With sufficient tinkering around, mostly removing the device and then re-pairing with PIN 0000 option,
I can sometime get the device to work and even enter the High Fidelity A2DP mode, but the exact working sequence seems to be unpredictable. I also upgrades my Fujitsu Amilo PA3553 64bit from Ubuntu 12.04 LTS to 14.04 LTS, but the same device seems to work correctly there. I'd be happy to attach logs, if anyone can advise what should be captured. -Colum

Had the same problem fixed it with:
"pactl list cards short" to get the device id
then I did "pactl set-card-profile x a2dp"
where X is your device id

found it by reading
http://askubuntu.com/questions/203272/no-a2dp-streaming-audio-from-12-04-to-bluetooth-headset

During different states of updates in Ubuntu 14.04 I experienced all bugs from original bug description (pairing works, but no audio) and also from comment #1 and comment #4 (pairing does not work, no devices found).

This actually solved my problems:

sudo mv /etc/bluetooth /etc/bluetooth.backup
sudo apt-get install --reinstall bluez

After a reboot everything is working again. The /etc/bluetooth directory is empty now.

If this does not work for you, just move back the bluetoth.backup directory to it's original place.

I've tried any and all solutions, nothing works. it was working flawlesly with 13.10. I'm thinking about ditching bluez and trying another app, anyone had success with blueman?

I just tested it off a xubuntu 14.04 image, and it works as intended with blueman, its clearly a bluez issue. If i use blueman under ubuntu without removing bluez, things get confused, but at least it recognizes the device. My guess is that removing bluez will solve things altogether, the problem is that bluez is tied to everything-buntu so its really -not- a option. No solution so far.

In my 14.04 bluez seems to be connecting ok. My headset connects with headset profile but I don't have audio devices to actually direct streams to the headset. This appears pulseaudio related. Listing the modules with "pactl list" I cannot find "bluetooth-device" and only my default audio sink. When I try to "pactl load-module module-bluetooth-device" directly it says "Failure: Module initialization failed".
I had some success when I did "pactl load-module module-bluetooth-discover" it loaded the discover and device module and created an audio sink. Unfortunately I now have my headset twice in audio settings and it will only do "headset" I can't put it to a2dp.
At least as a headset it is working now.

JoeD
My doesnt connect, doesnt discover, unless i use blueman, but you have to make sure pulseaudio-module-bluetooth is installed.

In Blueman i can select what it connects, and avoid the duplicate issue you described and connects to A2DP(audio sink).
It sometimes bugs out, and it has crashed my sound system-wise, but generally it can work.

@Omri Stein, @Akaname, @Kiori, @Joe D.

First some good news... There seems to be a simple workaround to restore the highquality A2DP interworking to your Bluetooth headset.

1) Use Blueman to pair to the headset. My experience was that it will pair and even connect as headset with the horrible audio
     quality "Telephony Duplex (HSP/HFP)" audio profile.
2) The Ubuntu Sound Control panel wont however show the Bluetooth device yet!
3) Open a command terminal and issue the command: pulseaudio -k
4) After a short delay you should see the Headset appear in the listed audio devices of the Ubuntu Sound Control Panel
5) Select the device and connect some audio source (VLC Media or your favourite player)... The quality will still be poor...
6) Now use Blueman GUI, select the device and press mouse right click and then select the "Refresh Services".
     It should show a succes message in the lower status bar.
7) Right click on the headset device in Blueman GUI and select Audio Sink. If it displays a success message your in luck.
8) Now right click the headset device in Blueman GUI and select Audio Profile menu and then select "High Fidelity Playback (A2DP)". It should suceed and switch into the correct mode.

==> You will always have to issue the "pulseaudio -k" command from terminal before using the headset, but it's a tolerable
        work around.

Hope this works for you too. -Colum

Colum,
After Blueman did its job, you have to activate the 'audio sink' component, personally i leave both on.
-But- after that you can just go to the sound options and switch to a2dp on the go, if blueman initiated audio sink, it will show up in the options, no need to use the audio profile route.
Ofcourse resetting pulse audio is a req. also.
Currently i have a2dp on the ears and the mic on, at the same time, because of this on the go switching in the sound options.
Its sad that Ubuntu doesnt use blueman or an implementation based on it, this could be one of those 'it just works' scenarios, without blueman it wont even pair my device...

CG: Many thanks for the tip. I had similar issues in Ubuntu 13.10
whereas 12.04 worked fine. I had hoped 14.04 would have solved it. I
also agree with you about Blueman. Without it I would have given up on
Bluetooth on Ubuntu long ago. Regards Colum :-D

Sent from my Windows Phone
From: Kiori
Sent: 23/04/2014 16:11
To: <email address hidden>
Subject: [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are
not working after last couple of updates
Colum,
After Blueman did its job, you have to activate the 'audio sink'
component, personally i leave both on.
-But- after that you can just go to the sound options and switch to
a2dp on the go, if blueman initiated audio sink, it will show up in
the options, no need to use the audio profile route.
Ofcourse resetting pulse audio is a req. also.
Currently i have a2dp on the ears and the mic on, at the same time,
because of this on the go switching in the sound options.
Its sad that Ubuntu doesnt use blueman or an implementation based on
it, this could be one of those 'it just works' scenarios, without
blueman it wont even pair my device...

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1283003

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in “gnome-bluetooth” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and
don't do anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1283003/+subscriptions

using sony vaio on ubuntu 14.04 and no devices found on when pairing. I have tried multiple devices too. One was a bluetooth headset and the other my samsung galaxy phone.

I then tried to see if my phone would see it visible if I turned the visibility to on on ubuntu but its still the same.

thanks
MorNando

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

Unbuntu 14.04 desktop 64bit. Standard install.

Motorola S805 BT headphones found, paired and connected fine.
Connects/disconnects automatically upon switching headphones on/off. BT lock icon shows connection status.
Headphones listed on output and input tabs in Sound Settings.

But...

System doesn't automatically select the headphones as output/input in Sound Settings.
Manually selecting the headphones in Sound Settings makes no difference, the sound still comes out of the amplified speakers and there is no recognition of input through the headphone mic.
So close...

If any logs required please instruct. Thanks

I confirm the problems.

I run Ubuntu 14.04 and it fails to route the sound to my external bluetooth speaker (Logitech UE Boom), which used to work nice and easy under 12.04.

The speaker is recognized and I can pair it with the computer . The service (Audio Sink) is recognized by Blueman, but it fails to connect and hence the external speaker, does not apear in the list of sound output devices.

Finally, I tried to install pulseaudio-module-bluetooth but this did not solve the problem either.

Is the following bug related?
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059

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

My problem was resolved by applying the sollution listed here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/comments/13 :

"The real issue was that module-bluetooth-discover was not loading (and still does not automatically)

Test by:
pactl list | grep -i module-bluetooth-discover

If empty load via
 pactl load-module module-bluetooth-discover

Pulse audio will then (hopefully) recognize the device"

I would like to thank Sebastian F (sf-lp) for pointing me in the right direction, as it seems the bugs were related (at least in my case).

The solution in last comment by RazTaz (qvovadis) worked for me (using Philips SounShooter)! I just need to find how to make it run at every login.

David, could you have a look to the pulseaudio side in case that's an issue there (see recent comments)

Ok, I first did a quick test here and my BT headset paired, showed up in sound settings, worked as usual, and profile was selectable. So at least the problem is not *that* generic.

Anyway, module-bluetooth-discover is loaded from /etc/pulse/default.pa, which is run every time pulseaudio starts. If it did not load, hopefully there is some related error in syslog.

So if you can verify that module-bluetooth-discover is indeed *not* loaded (i e does not show up in "pactl list modules"), hopefully there should be an error message in syslog indicating why it did not start. So, could you do a:
grep "pulseaudio.*bluetooth" /var/log/syslog
...to see if you find anything that looks suspicious?

Thanks!

Like you David, my BT headset is paired and connecting when switched on. The profile is also showing up in Sound Settings.

In my case though, the profile is not being autoselected in Sound Settings and manually selecting it does nothing. Sound is still routed through the wired amplified speakers.

pactl list | grep -i module-bluetooth-discover simply shows
Name: module-bluetooth-discover

Prior to switching on the headset: grep "pulseaudio.*bluetooth" /var/log/syslog shows nothing.

Post switching on the headset: grep "pulseaudio.*bluetooth" /var/log/syslog shows
pulseaudio[1928]: [pulseaudio] module.c: Module "module-bluetooth-discover" should be loaded once at most. Refusing to load.
pulseaudio[1928]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/716/hci0/dev_00_0C_55_D1_91_ED/fd0

Ok, so this is several bugs in one then...

 > pulseaudio[1928]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/716/hci0/dev_00_0C_55_D1_91_ED/fd0

For this error, if it appears when you're trying to switch to the headset, it looks like something on the bluez side. Look for bluez errors in syslog right above this line. Also make sure /etc/bluetooth/audio.conf is unchanged (in particular, the socket interface must remain disabled).

Incidentally, (follow-up from comment #33), in my case, "pactl load-module module-bluetooth-discover" as per RazTaz's post #29 simply throws up the message:
pulseaudio[1928]: [pulseaudio] module.c: Module "module-bluetooth-discover" should be loaded once at most. Refusing to load.

David, in response to comment #34 the log entries prior to the bluetooth error are showing:
Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy device is not possible.
Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)

I'm not exactly sure what to be looking for in the audio.conf file so, as it's not very big, I've attached it in case it provides any info. Modification date says 13 June 2012.

 > Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy device is not possible.
 > Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)

This indeed looks like the kernel is at fault. I don't know much bluetooth (I'm more into the audio side of things), so can't help further. Sorry.

I can confirm the problem exists with my hardware as well.

Medion MD86751, Ubuntu 14.04 with latest updates.

How do I report this upstream? I am fairly inexperienced with submitting bugs.

CG: @David:
        Could you please consider to reverse the status back from
'INCOMPLETE' to 'CONFIRMED' (again).

        There would /seem/ to be a real issue which has been confirmed
by several contributors
        in this thread...

         Regards Colum

On 29.04.2014 12:58, David Henningsson wrote:
>> Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy device is not possible.
> > Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)
>
> This indeed looks like the kernel is at fault. I don't know much
> bluetooth (I'm more into the audio side of things), so can't help
> further. Sorry.
>

Hi, I'm also having issues with Bluetooth on a fresh install of Ubuntu 14.04. I have the RT3290 chipset and had to patch and compile the Bluetooth driver from source. After installing the Bluetooth driver, the Bluetooth icon shows up as expected and I can try to pair with other devices. I tested with Logitech Bluetooth Headset for iPad2 and with a Siliphone Bluetooth Speaker. Both worked perfectly fine under Ubuntu 12.04. However, when I try to pair the devices I always get something like "Failure configuring device" (not this exact words because my Ubuntu is not in english). It happens with both. I also tried with bluez-simple-agent and I get the error "Creating device failed: org.bluez.Error.AuthenticationFailed: Authentication Failed". It never prompted me to input any passkey. When testing I also noticed that the Bluetooth tray icon gets a small lock next to it.

Me too. A have already connected my BT headset using Bluez and I can see it in the audio devices list. But when I trying to set it as audio input/output device then nothing happens.

I see this problem (the "re-auth of legacy device is not possible/Protocol not supported" one) when using a Motorola H300 headset which previous to 14.04 worked fine. On the same machine, a Samsung HM1700 works perfectly.

 > Could you please consider to reverse the status back from 'INCOMPLETE' to 'CONFIRMED' (again).

I will do so for PulseAudio if I get the requested information, which is:

"if you can verify that module-bluetooth-discover is indeed *not* loaded (i e does not show up in "pactl list modules"), hopefully there should be an error message in syslog indicating why it did not start. So, could you do a:
grep "pulseaudio.*bluetooth" /var/log/syslog
...to see if you find anything that looks suspicious?"

Other errors seem not to be PulseAudio's fault at this point.

i have the same issue using LG HBS-250

Few days ago after tinkering with bluetooth audio configuration I made to the point where nothing worked, headset wouldn't even connect. Then I replaced broken audio.conf with https://launchpadlibrarian.net/174137125/audio.conf and forgot about it.

Today after I connected my headset i got AD2P up and running with no problems.

Steps that seem necessary:

1. Replace audio.conf with the one from https://launchpadlibrarian.net/174137125/audio.conf
2. Reboot your computer
3. Remove your bluetooth headset from paired devices
4. Pair your bluetooth headset again.

I have no idea why it worked, but next time I'll grep all I can and put it here.

So as for now Medion MD86751 problem seems to have fixed itself.

Thanks for posting that Martin, I hope it helps others.

Unfortunately, that audio.conf file seems to be the same as mine from standard (attached in post #36) but in my case I still can't route through my headphones even though the system is showing it as paired and connected. Manually selecting the headphones in Sound Settings still has no effect. I've even removed the headphones and paired them. Strangely though I've never been asked for a pin number.
Did you do anything else other than change the audio.conf file?

Regards

I know that - it was my attempt to restore original configuration and forget about it until some sort of fix is available.

Unfortunately I have no idea what caused my machine to act different this time. The only thing that changed is that I have played music from youtube using chromium and flash plugin instead of movie in vlc.

bluetooth-discovery was running in both cases, and shortly before I got AD2P working I disconnected and reconnected my bluetooth dongle (although I tried that before and it didn't work).

There is nothing else I can think of, but I will visit this bug and try to help if there is anything I can do.

Sorry for a delayed response to comment #43. The suggested command:
grep "pulseaudio.*bluetooth" /var/log/syslog
produced NO OUTPUT.

The output from "pactl list" is uploaded as attachment, but there is no sign of any entry with text:
module-bluetooth-discover

-Colum

@Colum, thanks. Could you try the following:
edit /etc/pulse/default.pa and above the line that says "### Automatically load driver modules for Bluetooth hardware", add a line with this text:
set-log-level 4

Reboot your computer and confirm that the bug is still present. Then do a
grep pulseaudio /var/log/syslog > /tmp/syslog.txt

and then attach /tmp/syslog.txt here. Thanks!

(Afterwards you might want to restore default.pa to avoid your syslog being flooded with debug messages.)

CG: Seeing this quite late tonight. I will try to action your request
soon. BR. Colum
On 11 May 2014 22:20, "David Henningsson" <email address hidden>
wrote:

> @Colum, thanks. Could you try the following:
> edit /etc/pulse/default.pa and above the line that says "###
> Automatically load driver modules for Bluetooth hardware", add a line with
> this text:
> set-log-level 4
>
> Reboot your computer and confirm that the bug is still present. Then do a
> grep pulseaudio /var/log/syslog > /tmp/syslog.txt
>
> and then attach /tmp/syslog.txt here. Thanks!
>
> (Afterwards you might want to restore default.pa to avoid your syslog
> being flooded with debug messages.)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1283003
>
> Title:
> [Bluetooth + 14.04] Bluetooth headsets are not working after last
> couple of updates
>
> Status in “blueman” package in Ubuntu:
> Confirmed
> Status in “gnome-bluetooth” package in Ubuntu:
> Confirmed
> Status in “pulseaudio” package in Ubuntu:
> Incomplete
>
> Bug description:
> Hi,
>
> I found a bug in Ubuntu 14.04 !
>
> I tried to pair a bluetooth stereo headset (A2DP compatible). The
> pairing process goes well, but after that I can't select it on the
> audio preferences.
>
> When I select it, it only shows the last selected item options and don't
> do anything. (he should switch to the headset output).
> I must mention that it worked very well on Ubuntu 12.04.
>
> This bug can be in the bluetooth stack or in unity-control-center or
> maybe pulseaudio. I actually have no idea.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1283003/+subscriptions
>

@David ... I carried out the modification to the /etc/pulse/default.pa file as requested.
    I re-booted system and observed problem still on. After getting the Bluetooth Headset to
    pair with Blueman. Using sound control panel, the bluetooth headset still not recognised.
    Cannot get A2DP profile established. After I issue command: pulseaudio -k the headset
    appear in the sound control panel and after that I can get the A2DP to work. Log file attached
    as requested. - Colum

@Colum, thanks - from the log we can see that module-bluetooth-discover is unloaded manually. The program unloading it is "python2.7" which unfortunately does not tell us exactly from where this comes, just that it is some software written in python...

May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2501]: [pulseaudio] module-augment-properties.c: Looking for .desktop file for python2.7
May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2501]: [pulseaudio] module.c: Unloading "module-bluetooth-discover" (index: #8).
May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2501]: [pulseaudio] module.c: Unloaded "module-bluetooth-discover" (index: #8).

However, the answer is not far away. Here's what I found in blueman/plugins/applet/PulseAudio.py:

 for k, v in modules.iteritems():
                                if v["name"] == "module-bluetooth-discover":
                                        pa_utils.UnloadModule(k, lambda x: dprint("Unload module-bluetooth-discover result", x))

...so if blueman unloads module-bluetooth-discover, it's not PulseAudio's fault if it does not find new devices. Reassigning to Blueman.

CG: @David, OK & Thanks for your work to investigate/clarify this case.
Colum
On 14 May 2014 00:55, "David Henningsson" <email address hidden>
wrote:

> @Colum, thanks - from the log we can see that module-bluetooth-discover
> is unloaded manually. The program unloading it is "python2.7" which
> unfortunately does not tell us exactly from where this comes, just that
> it is some software written in python...
>
> May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2501]: [pulseaudio]
> module-augment-properties.c: Looking for .desktop file for python2.7
> May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2501]: [pulseaudio] module.c:
> Unloading "module-bluetooth-discover" (index: #8).
> May 13 19:58:09 gaynor-F1-22PTV1 pulseaudio[2501]: [pulseaudio] module.c:
> Unloaded "module-bluetooth-discover" (index: #8).
>
> However, the answer is not far away. Here's what I found in
> blueman/plugins/applet/PulseAudio.py:
>
> for k, v in modules.iteritems():
> if v["name"] ==
> "module-bluetooth-discover":
> pa_utils.UnloadModule(k, lambda x:
> dprint("Unload module-bluetooth-discover result", x))
>
> ...so if blueman unloads module-bluetooth-discover, it's not
> PulseAudio's fault if it does not find new devices. Reassigning to
> Blueman.
>
> ** Changed in: pulseaudio (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1283003
>
> Title:
> [Bluetooth + 14.04] Bluetooth headsets are not working after last
> couple of updates
>
> Status in “blueman” package in Ubuntu:
> Confirmed
> Status in “gnome-bluetooth” package in Ubuntu:
> Confirmed
> Status in “pulseaudio” package in Ubuntu:
> Invalid
>
> Bug description:
> Hi,
>
> I found a bug in Ubuntu 14.04 !
>
> I tried to pair a bluetooth stereo headset (A2DP compatible). The
> pairing process goes well, but after that I can't select it on the
> audio preferences.
>
> When I select it, it only shows the last selected item options and don't
> do anything. (he should switch to the headset output).
> I must mention that it worked very well on Ubuntu 12.04.
>
> This bug can be in the bluetooth stack or in unity-control-center or
> maybe pulseaudio. I actually have no idea.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1283003/+subscriptions
>

Updating my feedback.
I tried the above suggestions and indeed module-bluetooth-discover was not loaded by default, had to manually load it, but it makes no difference.

The bottom line is my headset works ok with blueman, but if i remove blueman and try built in standard bluez with standard gnome interface-pairing-nonesense, it doesnt work.

Perhaps the issue is with the gnome discoverer, because i cant pair, as in it wont recognize the device with it.
And its prob written in pythn right? its worth looking into ;).

Either way, its a bluez/gnome-not-sure-its-name discoverer/standard ubuntu interface problem.

At least for me

I'm struggling with this bug as well. My situation seems to be nearly the same as Kiori's, except that even with Blueman pairing the speaker successfully, it still doesn't show up in PulseAudio control.

It did work for a short while about a week ago, but then it stopped, and though I've tried to do everything I did before, and more, it hasn't worked again.

Pulseaudio-module-bluetooth is installed. Loading module-bluetooth-discover doesn't seem to help. Same with adjustments to audio.conf (though to get the device to pair, it seems that "sink" and "socket" must be enabled).

Update: I had success by following #15 from https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1181106.

What's new was modifying audio.conf with these lines:

[General]
Enable = Source,Sink,Headset,Gateway,Control,Media
Disable = Socket

HFP=false

[A2DP]
SBCSources=1
MPEG12Sources=0

And running:

pactl load-module module-switch-on-connect

Not entirely sure which part solved it. I note that disabling "socket" contradicts my last post.

Tried what Mr Lee said, and indeed its works nows. But the problem remains that crapware bluetooth-wizard is unable to pair the device, after its paired, the above setup works 'out of the box'.

The only downside so far is that without it, i could toy with blueman and get a2dp AND hsp or wahtever to be on -at the same time-. So i would have a mic on the headphone going AND the sound keeping a a2dp superior quality output at the same time.
Now with the given solution its either or, you cant have the esquizofrenia of being both things at once.

I'm gonna toy with the config and see what happens.

On a side note though, canonical needs to make bluetooth-wizard 'an offer it cannot refuse'. ;)

Tried a few edits, the bottom line is that if we want both on at the same time, they both need to be loaded, which you can do with blueman, and i have no idea how to do this without it.

I'm posting about this, because its ideal to have the best sound AND your headphone's mic work at the same time right.

Its would-be basic situations like these that keep me quiet when people start bashing canonical, they do give linux a bad name, in spite of all the great stuff they've done, specially with unity.

Well, IMHO bluetooth is one big mess in ubuntu. I'm using a BT headset for nearly 7 years now, and it has NEVER worked without some quirks.

Even this would be OK for me, but the quirks differ not only between releases but also between updates. Hence you can never be sure if the headset will work on any day... (BTW, why the hell we are STILL sitting here with the legacy Bluez 4.x stack? I guess an upgrade to Bluez 5.x could not make the state of affairs more encumbering.)

The one and only good news that I've got that I SUCCESSFULLY USED MY BT HEADSET YESTERDAY (17.05.2014) on an up-to-date ubuntu 14.04/trusty. This is trick/quirk that made things work:

> pactl load-module module-bluetooth-discover

Given that, there are a couple of ticket out here that points into this direction:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/948613
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946449

As David said in post #34 there appears to be a number of bugs going on here.

I've not had any trouble pairing and connecting my BT headphones (Motorola S805) 'out of the box' but it simply won't route the output to them even manually through Sound Settings. I've tried a number of the solutions posted including those of RazTaz, Marcin and Mr Lee, all to no avail.
This is the first release since Feisty Fawn 7.04 (at least) that I haven't been able to get them working.
I use a BT USB dongle that still works in Windows XP and 7. Even so my post #36 would suggest Ubuntu now sees this as a hardware issue in my case with the messages:
Apr 29 09:06:52 Voyager kernel: [ 2013.010319] Bluetooth: re-auth of legacy device is not possible.
Apr 29 09:06:55 Voyager bluetoothd[716]: Protocol not supported (93)

@aanno
Bluez 4 is being used because 5 lacks many needed features, such as having the headphone and mic working at once.
The devs say its working, but i've read its really not. I read a few months ago that the guys at pulse audio were working to change that, maybe in a few months we'll see the results.
So bluez 4 is kept for greater feature parity and common sense. plus i read that bluz devs are rather nutty. but that might be just gossip.

Another update... I've lost the connection twice now. It works for a couple days, then breaks. Now I'm at the point where Blueman doesn't even find the device. I've been playing with it--reversing, repeating, reinstalling--but I can't get it back.

Bearing in mind that I know next to nothing about this sort of thing, it seems to be Python-related. I use Quodlibet (written in Python), and one time the Bluetooth speaker connection seemed to break immediately on closing Quodlibet.

Bluetooth working well for a headset on 12.04, not working on 14.04, either as new install or as upgrade. It pairs normally, but on one machine (new install) does not appear in sound settings, on the other it appears but in neither case does it switch sound from speakers to the headset when on.

Bluetooth worked well in 13.04 and 13.10, but after upgrade to 14.04 it does not work anymore.
I am using a generic USB dongle (CSR) on an old 32 bit system.

grep "pulseaudio.*bluetooth" /var/log/syslog
 pulseaudio[3094]: [pulseaudio] module.c: Module "module-bluetooth-discover" should be loaded once at most. Refusing to load.

pactl load-module module-bluetooth-discover
Failure: Module initialization failed

would be nice, if bluetooth could work again

update:
After power down and restart this morning I tried again:
Bluetooth recognized my paired headset as connected, displayed the lock in the icon, but in sound settings the headset did not show up, no sound from headset.
After
  pactl load-module module-bluetooth-discover
  24
After that the headset is connecting and functioning.

So, it seems, sometimes BT can be activated directly after reboot by loading its discovery module (which in my case returned 24).

syslog entries:
grep "pulseaudio.*bluetooth" /var/log/syslog
Jun 4 09:57:52 xxx-Linux pulseaudio[3248]: [pulseaudio] module-bluetooth-device.c: 12:02:21:B1:40:5E is not known.
Jun 4 09:57:52 xxx-Linux pulseaudio[3248]: [pulseaudio] module.c: Failed to load module "module-bluetooth-device" (argument: "address=12:02:21:B1:40:5E profile=hsp"): initialization failed.

However, the headset seems to work properly if the command
   pactl load-module module-bluetooth-discover
is executed directly after startup/login before any paired BT device tries to connect - from a terminal window, returning "24".
It should be called automatically, but that doesn't seem to happen, or, something unloads it automatically. Syslog has no entry for module-bluetooth-discover.

Btw., Blueman seems to screw up in this case, so I don't use it.

Neither does not work with a bluetooth headset BeeWi BBh100. Not in headset mode, and not in a2dp mode.

Well I now have BT working in A2DP mode. Hopefully it will stay working. There was never any problem pairing or connecting, just no sound would come out and the sound settings screen did not offer any choices.

So, once paired and "pulseaudio -k" issued (but I don't know if that is needed or not):

In the Sound Settings window, the headset is visible but does not offer any options to choose a profile.

In bluetooth settings, pairing is shown but not profiles

However, found by accident, right-clicking on the entry in the Blueman screen offers the option to select an audio profile. This was set to 'none' by default (why I cannot imagine). Setting it to High Fidelity fixed the problem immediately.

Why have default settings that cannot produce the output that every user is going to need? Weird. And why have both sound settings and bluetooth settings screens, and yet the crucial function is on a blueman screen that does not come up when looking at the settings? Bluetooth settings and blueman should be merged.

There still remains the problem that the sound settings screen does not allow the profile to be selected, though it did in 12.04.

The other problem of course is that there are no definitive and reliable user functional instructions for this (or indeed most of Ubuntu) and major searching of individual users problems and attempted fixes is needed to find clues. 14.04 is an LTS release and all this stuff should 'just work'. Using Ubuntu is more like a research project than using a working system.

I appreciate that lots of people give up their effort to develop Ubuntu and other distros, and that is appreciated. But things that work (as all this did in 12.04) should not be tinkered with until they then fail.

Now I feel better.

What is disturbing here is the fact that this bug is unassigned or (in case of pulseaudio) marked invalid.
That means nobody feels responsible and takes care.
We - most probably - will have to wait a long time for this problem to be solved.

Since the manual loading of module-bluetooth-discover seems to help in my case, is there a simple way to automatically load it at log-in?

Well, since the Linux kernel and PulseAudio both are in main and officially supported, but blueman is not, and one of the problems seems to be that blueman unloads module-bluetooth-discover,
how well do things work *without* blueman?

I e, uninstall blueman and reboot and see how well the headset works. It probably won't fix your bug if there is a kernel error (such as "protocol not supported" or "re-auth of legacy device not possible"), but if the problem is only that module-bluetooth-discover does not load, then removing blueman should fix that.

Hi Blueman developers,

This is an outreach for help - let me know if this is the right channel
or not. We seem to have a lot of people claiming that pulseaudio's
module-bluetooth-discover is not loaded on startup on 14.04. This causes
problems with bluetooth headsets.

Reading the code I can see that blueman deliberately unloads
module-bluetooth-discover. Do you have a better idea than just removing
those lines of code, which probably are there for a reason?

Here are some related bugs:

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003

--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

Hi all,
I have been following this discussion for a while because the connection to my A2DP device was broken after upgrading to 14.04 with all the symptoms described above.

Following David Henningsson's suggestion in post #71, I used "apt-get purge blueman" to fully uninstall blueman from my system. After a restart, I could connect to the A2DP device with the Unity-default tool and the connection would not break down after ~1s anymore. The system did not switch the audio output to this device automatically, but after manual switch audio output was just fine.

So in short: Uninstalling blueman solved my bluetooth connection problem, which confirms that it is causing this issue.

I created an upstream bugreport for blueman:
https://github.com/blueman-project/blueman/issues/64

Thanks Sebastian! Based on what was written in the github report, I've just commented out the module unloading that blueman does, built the result and put it in a ppa here:

https://launchpad.net/~diwic/+archive/bluemantest

It is possible that blueman messes with more stuff so that just commenting out this part does not resolve the problem, but it's worth a try.

So, anybody wants to try the blueman in this ppa, reboot, and see if this fixes the headset pairing issue?

Hi David,

I'm not expecting bluemantest to actually resolve my problem as I can already pair and connect but not route to my headphones. Anyway anything is worth a shot at the moment so I tried to install the file through Synaptic but am getting a fail with the message "E: blueman: subprocess installed post-installation script returned error exit status 101". The program seems to have partially installed but won't run.
The log is reporting:
Processing triggers for man-db (2.6.7.1-1) ...
Setting up blueman (1.23-git201403102151-1ubuntu2~diwicppa) ...
Sorry: IndentationError: expected an indented block (PulseAudio.py, line 235)
dpkg: error processing package blueman (--configure):
 subprocess installed post-installation script returned error exit status 101
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up blueman (1.23-git201403102151-1ubuntu2~diwicppa) ...
Sorry: IndentationError: expected an indented block (PulseAudio.py, line 235)
dpkg: error processing package blueman (--configure):
 subprocess installed post-installation script returned error exit status 101
Errors were encountered while processing:
 blueman

Furthermore, as a point of confirmation I didn't have the official Blueman Manager installed when I could connect/pair and see my headphones in Sound Settings. As soon as I installed the official Blueman my headphones no longer appeared Sound Settings.

Also, I tried Stuart's solution (post #69) but it refused to allow me to specify the High Fidelity option by keeping switching it back to Off.

Regards

 > Sorry: IndentationError: expected an indented block (PulseAudio.py, line 235)

Oops, then I screwed up. Please do not use the package.

a hacking fix:

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/comments/31

#78 > a hacking fix:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059/comments/31

That causes Blueman to crash at startup, but for Pulseaudio, it seems tyo work.

@Harmut (hesse-hsr)
    Thank you! I just tried your "hacking fix" and it works very nicely indeed :) .
    Now the bluetooth headset shows up fine in the sound settings panel
    and I can switch on A2DP profile; without problems.

    Incidently, I did not encounter the reported Blueman crash, which
   @Hartwig Kolbe reported.

    Hopefully Blueman developers will finally try to issue a permanent fix!
    Thanks again also to @David for his discovery of the failure root cause.
    - Colum

Thank you Hartmut, this works for me too.

In addition to rebooting I also had to remove and then re-add/pair/connect/select the headphones in Sound Settings/switch to A2DP before the headphones would work.

As a note there are some peculiar quirks for me:

For some reason I have 2 headphone entries in Sound Settings both in Output and Input tabs. Disconnecting the headphones removes both entries in both tabs.

Switching on the headphones shows a connection symbol in the Unity top activity bar without rerouting the sound from wired speakers. I have to manually connect through Blueman, specify the A2DP profile and select the headphones in Sound Settings every time I want to use the headphones.

Specifying the A2DP profile appears to be a bit hit and miss. Sometimes it works, other times it'll drop back to Off. Once it does 'catch' it holds without dropout.

Trying to access Sound Settings via the activity bar bluetooth icon stopped working when I installed Blueman. I can still access the settings via System Settings though.

All the above being said, this is a big step forward.

Cheers

> > Sorry: IndentationError: expected an indented block (PulseAudio.py, line 235)
> Oops, then I screwed up. Please do not use the package.

This should now be fixed. A new package is currently building in the ppa.

Guys lets just not forget that there are people that have issues with blueman, and people that have issues even without blueman(with bluez and gnome stuff instead).

Just making sure this wont be forgotten.

@David Henningsson

Hi David,
Have installed the new bluemantest from the ppa and for me it works. Thank you.

It works in the same way that editing the Pulseaudio.py file worked as specified by Hartmut. I.e. there are quirks (specified in post #81) to navigate to actually get the sound routed to the headphones, it's not simply a case of connecting the headphones and everything else is seamless.
In particular,
i) even after pairing/trusting the headphones in blueman I couldn't select the A2DP profile (pulseaudio[1926]: [pulseaudio] module-bluetooth-device.c: Profile not connected, refused to switch profile to a2dp; pulseaudio[1926]: [pulseaudio] module-bluetooth-device.c: Default profile not connected, selecting off profile) until I ran Setup for the headset in blueman
ii) had to manually select the headset in Sound Settings
iii) selecting the headset (Output tab) in Sound Settings caused A2DP to switch Off
iv) switching A2DP back on in blueman showed A2DP assigned in Sound Settings (Output tab) UNTIL I went into the Input tab to select the headphones there and then A2DP dropped out in the Output tab. Selecting A2DP after the headset was selected in both Output and Input tabs allowed things to work as required.

@Kiori

Indeed. In my case the irony is that without blueman (which I originally didn't have installed) I couldn't get the headset to work at all. So despite blueman having problems of its own it has actually helped to resolve my problem to the extent where I can actually use the headset albeit by going around the houses.

Thank you, David!
I installed blueman from your ppa (#75), reboot, and all works fine.
(Mint 17 (2014-03) Mate 32bit)

With the Blueman package from Davids PPA, I'm able to connect with my bluetooth speakers again. I only have to choose them manually as default output.
On a sidenote: The Blueman deb should depend on pulseaudio-module-bluetooth. I removed it previously (or it isn't even installed as default on Xubuntu, I'll have to check that). So people testing this package: make sure you have pulseaudio-module-bluetooth installed, if it doesn't work.

I suffer the same symptoms. Used it in 14.04 (Ubuntu GNOME over here) and stopped working (though I did change lots of PPAs). Device is detected, paired correctly but it won't show up in Preferences > Sound.

Running 'paclt list cards short' (per #14) does not list this (only the built-in card), while in Preferences > Bluetooth device shows up as paired (and device responds accordingly). Weirdly, sometimes the toggle "Bluetooth" in Preferences > Bluetooth shows up as disabled, while the device acts like it is indeed paired (so it is enabled actually).

I've also found this on /var/log/syslog:

> Jun 20 20:10:51 valinor bluetoothd[20013]: Adapter /org/bluez/20013/hci0 has been enabled
> Jun 20 20:10:51 valinor bluetoothd[20013]: Unknown command complete for opcode 19
> Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPAG
> Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/HFPHS
> Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSource
> Jun 20 20:10:51 valinor bluetoothd[20013]: Endpoint registered: sender=:1.57 path=/MediaEndpoint/A2DPSink
> Jun 20 20:11:17 valinor bluetoothd[20013]: Adapter /org/bluez/20013/hci0 has been disabled
> Jun 20 20:11:17 valinor bluetoothd[20013]: Adapter /org/bluez/20013/hci0 has been enabled
> Jun 20 20:11:20 valinor bluetoothd[20013]: Discovery session 0x7f2e86c14df0 with :1.149 activated
> Jun 20 20:11:27 valinor bluetoothd[20013]: Unknown command complete for opcode 37
> Jun 20 20:11:30 valinor bluetoothd[20013]: Stopping discovery
> Jun 20 20:11:33 valinor bluetoothd[20013]: Badly formated or unrecognized command: AT+CBC=63
> Jun 20 20:11:33 valinor bluetoothd[20013]: Badly formated or unrecognized command: AT+BIA=0,0,1,1,1,1,0,`

These last two lines look suspect, perhaps they're useful somehow.

Sorry for my english. I have two bluetooth devices, a headphone and a bluetooth audio receiver that i bought in china. The first device pair but a cannot select the profile a2dp, it only work for the first time when a add a device, after on reconnect it wont work anymore. The second device work flawless, every time a turn it on, it's recognize and the sound output automatic change to device and the profile to a2dp.

I discovered a solution which worked for me. It is from this youtube video http://www.youtube.com/watch?v=YgFoWmeFqaI .
All you have to do is :
1- Install PulseAudio Volume Control from Ubuntu Software Center
2- Open it and select Configuration tab
3- Switch the paired Bluetooth device's Profile from Off to A2DP
At the moment, it seems you may have to repeat steps 2 and 3 every time you connect the bluetooth device or open a music app.

-------------------------------------------
Guys if you're still having issues and using gimmicks i guess you missed the post that talked about adding this:
[General]
Enable = Source,Sink,Headset,Gateway,Control,Media
Disable = Socket

HFP=false

[A2DP]
SBCSources=1
MPEG12Sources=0

To audio.conf.
---------------------------------
So what does that mean?
It means type at the terminal : sudo gedit /etc/bluetooth/audio.conf
(assuming you're on ubuntu, if not use Kate, or mousepad, etc.)
 And add the above lines in each corresponding section.
So basically my current audio.conf is like this:

# Configuration file for the audio service

# This section contains options which are not specific to any
# particular interface
[General]
Enable = Source,Sink,Headset,Gateway,Control,Media
Disable = Socket

#Enable=Gateway

# Switch to master role for incoming connections (defaults to true)
#Master=true

# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Gateway,Source,Socket
#Disable = Socket

# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM

# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true

# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
[Headset]

# Set to true to support HFP, false means only HSP is supported
# Defaults to true
HFP=true
#HFP=false

# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
MaxConnected=1

# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incoming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false

# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0

-----------------------------------------------------
The bad part about this is that it completely fixes A2DP as a standard, so i cant have both modes at once, which would mean having the mic and high quality sound at the same time, but its better than nothing right.

Beyond that the only major software problem that i still see is that gnome-discovery or whatnot is incapable of pairing any device i throw at it, so we are all forced to use 'Blueman' the mighty savior for the win.

In case your lazy or did not understand, i added my audio.conf to the comment for easy testing.
Download it and copy it to /etc/bluetooth/ , also remember to backup your existing audio.conf in case you're not used to this sort of thing.
If you don't know how to copy this in root-protected folders, simply type "sudo nautilus" at the terminal and have fun.

Best wishes to all,
still hoping for the day canonical gives gnome the finger.
Seriously, why couldn't they have based ubuntu on KDE in the first place?
Oh ...

Also, remember that after you set that and basically restart, when you're all set and your bt headset is paired you still have to go to sound options and select it as an output and select A2DP or you won't be getting any sound out of it.
Every time you play with something you have to go back there and set your headset as the output again. ;)

Alternatively, this restarts bt for the system:
sudo service bluetooth restart

And this restarts pulseAudio:
pulseaudio -k

Use as needed.
Cheers

Hi all,

blueman maintainer here. I understand this is not 100 % a blueman problem, but blueman is definitely having its part.

As you found out, there is a blueman applet plugin that unloads pulseaudio's bluetooth-discover module and handles devices manually. The original author let me know that this is due to pulseaudio (the discovery module especially) not working well back then. For more details see https://github.com/blueman-project/blueman/issues/64

I've prepared a blueman version without that pulseaudio applet plugin, but still including the manager plugin. That one is responsible for selecting the A2DP profile. Although there are other ways to do this (e.g. PulseAudio Volume Control as mentioned above), it seems like this is a useful feature to some users.

You can test the changes using the following PPA:

https://launchpad.net/~cschramm/+archive/blueman

The code can be found in the nopahandling branch:

https://github.com/blueman-project/blueman/tree/nopahandling

Cheers

Hi cschramm,

Have installed your ppa version of Blueman and it is not working for me.

The manager allows me to find, pair and connect to my headphones but there is no entry in Sound Settings (there was before) to allow me to route to the headphones.

In addition I now have 2 bluetooth icons on the top activity bar (Unity desktop) showing different option. 1 is the standard bluetooth options, the other is new and contains options to sned and browse files to the device, local services, plugins, etc.

The following code is from var/log/syslog, I'm not exactly sure what, if anything is relevent.

Regards

Jun 26 10:12:32 Voyager blueman-mechanism: Starting blueman-mechanism
Jun 26 10:12:32 Voyager dbus[697]: [system] Successfully activated service 'org.blueman.Mechanism'
Jun 26 10:12:33 Voyager blueman-mechanism: loading Network
Jun 26 10:12:33 Voyager blueman-mechanism: loading RfKill
Jun 26 10:12:33 Voyager blueman-mechanism: loading Config
Jun 26 10:12:33 Voyager blueman-mechanism: loading Ppp
Jun 26 10:12:33 Voyager bluetoothd[734]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/HFPAG
Jun 26 10:12:33 Voyager bluetoothd[734]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/HFPHS
Jun 26 10:12:33 Voyager bluetoothd[734]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource
Jun 26 10:12:33 Voyager bluetoothd[734]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink
Jun 26 10:12:33 Voyager bluetoothd[734]: hci0: Remove UUID (0x0011) failed: Busy (0x0a)
Jun 26 10:13:02 Voyager blueman-mechanism: Exiting
Jun 26 10:14:36 Voyager bluetoothd[734]: Discovery session 0x7f42550c3ac0 with :1.96 activated
Jun 26 10:14:39 Voyager bluetoothd[734]: Unknown command complete for opcode 37
Jun 26 10:14:46 Voyager bluetoothd[734]: Stopping discovery
Jun 26 10:15:29 Voyager pulseaudio[1908]: [pulseaudio] module-bluetooth-device.c: 00:0C:55:D1:91:ED is not known.
Jun 26 10:15:29 Voyager pulseaudio[1908]: [pulseaudio] module.c: Failed to load module "module-bluetooth-device" (argument: "address=00:0C:55:D1:91:ED profile=hsp"): initialization failed.
Jun 26 10:17:01 Voyager CRON[3005]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jun 26 10:17:04 Voyager bluetoothd[734]: Unable to select SEP
Jun 26 10:17:04 Voyager kernel: [ 343.203153] input: 00:0C:55:D1:91:ED as /devices/virtual/input/input10
Jun 26 10:17:05 Voyager acpid: input device has been disconnected, fd 16
Jun 26 10:17:28 Voyager kernel: [ 367.422005] input: 00:0C:55:D1:91:ED as /devices/virtual/input/input11
Jun 26 10:48:51 Voyager dbus[697]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Jun 26 10:48:51 Voyager dbus[697]: [system] Successfully activated service 'org.freedesktop.hostname1'

@cschramm
The package from your PPA (version 1.23-git201406261335-deb-1) works for me (on XFCE, no gnome-bluetooth installed). Pairing with speakers is possible and i'm able to select them in pavucontrol and play back audio.
I have to do this manually, so the PulseAudio manager plugin doesn't seem to work, yet (I have "Move streams" and "Make default sink" enabled).

Upon connect I get the following error in syslog:
Jun 26 15:21:33 laptop pulseaudio[1364]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/753/hci0/dev_00_0D_18_A0_16_50/fd2

and upon disconnect:
Jun 26 15:23:45 laptop pulseaudio[1364]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/753/hci0/dev_00_0D_18_A0_16_50/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist

The nopahandling does not include the plugin, while the deb version does and only hasn't got the pulseaudio module unload. So it should be identical to David Henningsson's PPA version.

Since the nopahandling branch did not work for zig59, I'm going for this minimalistic approach. Although I'm not sure how pulseaudio could work with other tools like gnome-bluetooth then, since they do not employ any specific pulseaudio handling at all...

The syslog messages are probably a result of blueman competing with the discovery module for the initialization of the devices. I'm not sure if the source redirection (that's the rest the applet plugin is responsible for) will even work if blueman cannot load the device module itself. Looking at the source I do not think so, but then it should not make a difference to just remove the module-bluetooth-discover unload or remove the whole PulseAudio applet plugin...

@zig59, please post you audio.conf.

To me the new ppa blueman is working flawlessly, and it doesnt bug out on me anymore, it used to crash now and then. However, before using it I was careful to get my audio.conf back to its original state of basically no config, so it leaves everything to blueman.

And btw the second icon that you get IS blueman.

@cschramm
Good job so far man.

When using the deb version (1.23-git201406261335-deb-1) and running blueman-applet in a terminal, what output do you get?

There should be things like:

    Starting source redirector
    Found source
    Source not found :(
    module-loopback load result
    Loopback module unload result
    Destroying redirector

And some IDs from the Module class. Basically every output from the PulseAudio.py file is relevant.

@Kiori

audio.conf is attached. This is as installed as standard as far as I know.

@cschramm

As a simple user I'm starting to get out of my depth with the diagnostic procedures, please bear that in mind if I've misinterpreted your instructions.
When I originally ran blueman-applet in terminal I got:
Loading configuration plugins
blueman-applet version 1.23 starting
There is an instance already running

So issuing killall blueman-applet and then reissuing blueman-applet I did not get any of the output you specified, simply a load of app load and initialisation messages. I've copied these into the attached file.

I've also included the relevant part of var/log/syslog although there's not much to see.

Apologies in advance if there is a delay over the next few days. I may be able to get back online on Sunday.

Regards

Thanks for the output!

Did you connect the audio device? Then it looks like the applet plugin indeed does not do anything... But then again the version without the plugin (1.23-git201406231750-nopahandling) should not make any difference... :/

@cschramm

I've just received a new version of the ppa which seems to include additional debugging messages.

I've attached the output from the new version

Regards

@cschramm

I just installed the blueman package from your ppa and it works for me. Thanks a lot :-)

For people who still have issues, see #92.

That blueman ppa version works for me, also.
But, I had to reboot to have it working, restarting blueman and pulseaudio did not do the job.
Strange enough that it now works with blueman. Despite i never use blueman, its startup seems necessary.

Today for whatever reason after a few updates(sadly i didn't check what was updated) BT no longer works.

Tried a few commands, like restarting pulse, removed blueman, you name it, i prob did it. Nothing even worked.
Here is the end result:

Jun 30 01:05:00 lorien bluetoothd[705]: Adapter /org/bluez/705/hci0 has been disabled
Jun 30 01:05:01 lorien ntpdate[2543]: adjust time server 91.189.94.4 offset 0.365796 sec
Jun 30 01:05:02 lorien bluetoothd[705]: Adapter /org/bluez/705/hci0 has been enabled
Jun 30 01:05:09 lorien NetworkManager[765]: <info> (wlan0): IP6 addrconf timed out or failed.
Jun 30 01:05:09 lorien NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 30 01:05:09 lorien NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 30 01:05:09 lorien NetworkManager[765]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 30 01:06:37 lorien pulseaudio[1721]: [pulseaudio] module.c: Module "module-bluetooth-discover" should be loaded once at most. Refusing to load.
Jun 30 01:06:59 lorien bluetoothd[705]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/HFPAG
Jun 30 01:06:59 lorien bluetoothd[705]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/HFPHS
Jun 30 01:06:59 lorien bluetoothd[705]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSource
Jun 30 01:06:59 lorien bluetoothd[705]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSink
Jun 30 01:06:59 lorien bluetoothd[705]: hci0: Remove UUID (0x0011) failed: Busy (0x0a)
Jun 30 01:06:59 lorien rtkit-daemon[1231]: Successfully made thread 2688 of process 2688 (n/a) owned by '1000' high priority at nice level -11.
Jun 30 01:06:59 lorien rtkit-daemon[1231]: Supervising 1 threads of 1 processes of 1 users.
Jun 30 01:07:00 lorien rtkit-daemon[1231]: Successfully made thread 2689 of process 2688 (n/a) owned by '1000' RT at priority 5.
Jun 30 01:07:00 lorien rtkit-daemon[1231]: Supervising 2 threads of 1 processes of 1 users.
Jun 30 01:07:00 lorien rtkit-daemon[1231]: Successfully made thread 2690 of process 2688 (n/a) owned by '1000' RT at priority 5.
Jun 30 01:07:00 lorien rtkit-daemon[1231]: Supervising 3 threads of 1 processes of 1 users.
Jun 30 01:07:00 lorien bluetoothd[705]: Endpoint registered: sender=:1.99 path=/MediaEndpoint/HFPAG
Jun 30 01:07:00 lorien bluetoothd[705]: Endpoint registered: sender=:1.99 path=/MediaEndpoint/HFPHS
Jun 30 01:07:00 lorien bluetoothd[705]: Endpoint registered: sender=:1.99 path=/MediaEndpoint/A2DPSource
Jun 30 01:07:00 lorien bluetoothd[705]: Endpoint registered: sender=:1.99 path=/MediaEndpoint/A2DPSink
Jun 30 01:07:12 lorien kernel: [ 261.550854] waiting module removal not supported: please upgrade
Jun 30 01:07:12 lorien kernel: [ 261.551214] waiting module removal not supported: please upgradewaiting module removal not supported: please upgrade
Jun 30 01:07:37 lorien rtkit-daemon[1231]: Successfully made thread 5347 of process 5347 (n/a) owned by '1000' high priority at nice level -11.
Jun 30 01:07:37 lorien rtkit-daemon[1231]: Supervising 4 threads of 2 processes of 1 users.
Jun 30 01:07:37 lorien ...

Hi cschramm and thanks for looking at this bug!

How do you think we should proceed to release a fix/workaround? Should we just upload the code that disables the module unload, or do you have a better suggestion?

Disabling the unload is the best guess yet, although I do not know how and why the rest of the plugin can still work then. ;) But I can figure that out afterwards.

(If anybody wants to help with that, please send me the blueman-applet output of when you successfully connect your audio device using the 1.23-git201406261335-deb version. The best place to discuss this is probably the upstream ticket: https://github.com/blueman-project/blueman/issues/64)

@David: If you like I'll push the fix to Debian testing. That's probably the cleanest way to also get it into Ubuntu, isn't it?

 > @David: If you like I'll push the fix to Debian testing. That's probably the cleanest way to also get it into Ubuntu, isn't it?

Sounds like a plan, thanks!

Not sure if we sync from Debian unstable or Debian testing these days, but I assume you upload the fix to both. That will bring it into utopic. After that we can SRU it into trusty.

It's now in Debian unstable and should automatically make it into testing in about 10 days. Ubuntu probably syncs from there.

Hi there, still can't connect anymore, with or without blueman.
got this in the log "bluetoothd[766]: Connection refused (111)"
And found this bug:
https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/198494

Might be related, there might be more out there.

Cheers.

I still get this:

blueman-mechanism: Starting blueman-mechanism
dbus[709]: [system] Successfully activated service 'org.blueman.Mechanism'
 blueman-mechanism: loading Network
 blueman-mechanism: loading Config
 blueman-mechanism: loading Ppp
 blueman-mechanism: loading RfKill
 bluetoothd[772]: Adapter /org/bluez/772/hci0 has been disabled
 bluetoothd[772]: hci0: Set Powered (0x0005) failed: Busy (0x0a)
 bluetoothd[772]: Adapter /org/bluez/772/hci0 has been enabled
 blueman-mechanism: Exiting
 bluetoothd[772]: Connection refused (111)
 bluetoothd[772]: Connection refused (111)
 bluetoothd[772]: Unable to select SEP

Even if i remove and thereafter setup the device again this still happens. its sad because bluetooth was working flawlessly. :/

Today it worked again. I tried connecting as headset instead of a2dp and it worked, but no high def audio, then i typed:
sudo pactl load-module module-bluetooth-discover
and it returned:
26
whatever that means, after that, got full a2dp BT sound again...
So clearly there is a pulseaudio issue still lurking around the block... :/

@cschramm

Despite originally not working (post #93) the ppa version of blueman is now working without me doing anything (possibly simply a reboot was needed). I'm also only getting one Headset entry in Sound Settings whereas previously I was getting two.

The system connects upon powering up the headphones but to route the sound I have to select the headset in Sound Settings and then select the A2DP profile in Blueman. Easy enough.
Oddly, entering Sound Settings AFTER the sound is routed through the headphones still shows the amplified speakers selected rather than the headset. Similarly, on the Input tab the default microphone is selected rather than the headset

var/log/syslog is showing the following entries:

Jul 8 09:12:07 Voyager kernel: [ 633.477148] Bluetooth: re-auth of legacy device is not possible.
Jul 8 09:12:08 Voyager bluetoothd[789]: Protocol not supported (93)
Jul 8 09:12:08 Voyager pulseaudio[1900]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/789/hci0/dev_00_0C_55_D1_91_ED/fd0
Jul 8 09:12:09 Voyager kernel: [ 635.526503] input: 00:0C:55:D1:91:ED as /devices/virtual/input/input10
Jul 8 09:12:50 Voyager bluetoothd[789]: message repeated 2 times: [ Protocol not supported (93)]
Jul 8 09:13:15 Voyager bluetoothd[789]: /org/bluez/789/hci0/dev_00_0C_55_D1_91_ED/fd1: fd(27) ready
Jul 8 09:13:15 Voyager rtkit-daemon[1383]: Successfully made thread 10274 of process 1900 (n/a) owned by '1000' RT at priority 5.
Jul 8 09:13:15 Voyager rtkit-daemon[1383]: Supervising 5 threads of 1 processes of 1 users.
Jul 8 09:13:15 Voyager kernel: [ 701.111148] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.156165] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.157136] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.210194] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.237160] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.244081] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.252141] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:13:15 Voyager kernel: [ 701.270153] Bluetooth: Unexpected continuation frame (len 0)
Jul 8 09:11:02 Voyager dbus[744]: message repeated 3 times: [ [system] Reloaded configuration]
Jul 8 09:13:55 Voyager dbus[744]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper)
Jul 8 09:13:55 Voyager dbus[744]: [system] Successfully activated service 'org.freedesktop.hostname1'

Regards

I think you're always gonna have to choose the BT headset, because you just mounted it.
If you're using ubuntu in sound settings you can set a2dp, provided its already active(as in set through blueman or whatnot).
Also bear in mind that having a2dp means no mic on the headset, you have to use the other one for that.

I tried everything on this list up to comment #59 then it started working!

Bluetooth Headset: BT-BSH10 http://amzn.com/B0059NF3PU
Laptop: ASUS X201E 11.6" Celeron 4GB/320GB Ubuntu Laptop http://amzn.com/B00B1N92ZY
OS: Ubuntu 14.04 with all updates as of today.

On comment #29 I had to add the etc/bluetooth/audio.conf file, it did not exist.

I did this by going to:

https://launchpadlibrarian.net/174137125/audio.conf

Then use CRTL+A to highlight the entire file. Then CRTL+C to copy it.

Open the Terminal and type the command:

sudo gedit

Then paste the file in gedit with CRTL+V.

I made the same changes as comment # 29 but also uncommented:

Master=true

and

AutoConnect=true

Then use File->Save As from the menu to place it in etc/bluetooth directory.
It was necessary to use the arrow next to Usr to move up to the Home directory and then click it again when it changes to a hard drive icon. The etc directory will be visable now, click on it and then bluetooth, make the title audio.conf and click save.

After a reboot it started woking at comment #59 with the Terminal command:

pactl load-module module-bluetooth-discover

It responds with:
24

Bluetooth headset with buit-in microphone both work now.
I can see the Bluetooth headset in the PulseAudio Volume Control.
The Sound app now lists the Headset under the Input and Output tabs.

Thanks.

I went out of range and lost the connection. It would not reconnect.

Now when I run:

pactl load-module module-bluetooth-discover
Failure: Module initialization failed

I tried:

pulseaudio -k

pulseaudio -D
E: [pulseaudio] main.c: Daemon startup failed.

pactl load-module module-bluetooth-discover
19

Remove
Pair
Refresh Services
Audio Sink

Based on Comment #67 I rebooted and immediately ran :

pactl load-module module-bluetooth-discover
23

The headset is listed in the PulseAudio Volume Control and the Sound app.
It shows activity in the Bluetooth Manager

Still no sound in the headphones.

Then I check and see if the Connection indicator is on at the bluetooth icon with a lock on it at the top right of the main screen and it works again.

Thanks once more.

I don't know if my problem is related to this one bug (any ideas?), I'm having lots of problems with Bluetooth since the update to 14.04.

Just a few minutes ago, I turned my bluetooth headset on; it connected, I verified it was working correctly; I went to a Google Hangout... and the headset disconnected and I have not been able to reconnect it. (It does connect to my phone normally, so I think the headset is ok.)

It worked fine (with only minor issues) on 13.10 and previous.

I'm attaching an excerpt of my log. Any suggestions of what I can do next to find more details?

Should I create a new bug or do you think this is the same bug?

Jul 29 13:46:22 imac kernel: [ 9194.185587] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:23 imac kernel: [ 9194.269541] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:23 imac kernel: [ 9194.594437] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:23 imac bluetoothd[791]: /org/bluez/791/hci0/dev_00_23_7F_B4_82_57/fd0: fd(24) ready
Jul 29 13:46:28 imac bluetoothd[791]: Audio connection got disconnected
Jul 29 13:46:28 imac kernel: [ 9199.993603] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:28 imac kernel: [ 9199.997737] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:41 imac kernel: [ 9213.037178] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:46:42 imac kernel: [ 9213.298044] Bluetooth: Unexpected continuation frame (len 0)
Jul 29 13:47:21 imac kernel: [ 9252.736140] Bluetooth: hci0 SCO packet for unknown connection handle 6
Jul 29 13:47:21 imac kernel: [ 9252.736147] Bluetooth: hci0 SCO packet for unknown connection handle 6
Jul 29 13:47:21 imac kernel: [ 9252.736149] Bluetooth: hci0 SCO packet for unknown connection handle 6
Jul 29 13:46:59 imac bluetoothd[791]: Audio connection got disconnected
Jul 29 13:49:26 imac bluetoothd[791]: Unable to get service record: Connection timed out (110)

It is impossible to re-connect the headset after that.

Anything I can do to provide more data?

I confirm I can connect using Blueman. In that case though, I have to load the bluetooth module on PulseAudio manually.

I guess this is an acceptable work around for now, but it would be nice if it simply worked like it did on 13.10.

I can connect using Blueman... but if I actually use the headset it starts distorting the audio after a minute or so and then disconnects.

# 14 worked for me...
Had the same problem fixed it with:
"pactl list cards short" to get the device id
then I did "pactl set-card-profile x a2dp"
where X is your device id

found it by reading
http://askubuntu.com/questions/203272/no-a2dp-streaming-audio-from-12-04-to-bluetooth-headset

I discovered this problem this morning while trying to set up my laptop with a bluetooth headset (Moto S305) for a pending video conference. Some Googling led me to this thread and comment #93, and the fix works just fine. "Trusty" being a LTS release, there are sure to be many other people affected indefinitely until an update appears in the standard "Trusty" ppa's. Hope that will be soon.

This bug wasn't fixed yet.

Reading the comments it isn't clear the problem is on pulseaudio. In my case sometimes when I try to connect to my headset I get a crash on unity-control-center (not sure yet if it is related). After upgrading from Ubuntu 12.x I started to have this issue. I can pair my headset but when I try to connect it the system shows that the device is connected if you go on system tray menu and shows it is disconnected if you go through system settings -> bluetooth. But it don't work anyway.

Ubuntu 14.04 - Notebook Dell Inspiron 5748

There may be light at the end of the tunnel - Ubuntu 14.10 beta 1 as of 18 September is working properly for bluez streaming audio to my BT headset using a2dp properly. Headset is showing up under Settings>Sound. Now if they could just get Network Manager to work again...WiFi quit working.

This bug bugs me as well in 14.04 on all three family computers. My headsets pair, but bluetooth doesn't show up as an option in the Sound Settings. Irritating!

pactl load-module module-bluetooth-discover

work for me. lubuntu 14.04. How to fix it?
Try add this command to autostart, don't work. Only run command in console. Then i can connect bluetooth headset.

upstream ticket https://github.com/blueman-project/blueman/issues/64

Totally frustrating trying various 'solutions' that do not make a difference.

Unable to pair with headset under new 14.04 installation. Having attempted various recommended downloads, e.g. blueman, bluez, etc. have progressed to 'seeing' the device after a while, but pairing does not complete.

This is a Dell laptop. Bluetooth works fine under Windows partition on this same laptop, so not a hardware issue?

So many red herrings it appears, e.g. firmware?

Need a SOLUTION!

Nov 18 10:30:01 fuga4 bluetoothd[634]: Bluetooth daemon 4.101
Nov 18 10:30:01 fuga4 bluetoothd[634]: Starting SDP server
Nov 18 10:30:01 fuga4 bluetoothd[634]: DIS cannot start: GATT is disabled
Nov 18 10:30:01 fuga4 bluetoothd[634]: Failed to init deviceinfo plugin
Nov 18 10:30:01 fuga4 bluetoothd[634]: Failed to init proximity plugin
Nov 18 10:30:01 fuga4 bluetoothd[634]: Failed to init time plugin
Nov 18 10:30:01 fuga4 bluetoothd[634]: Failed to init alert plugin
Nov 18 10:30:01 fuga4 bluetoothd[634]: Failed to init thermometer plugin
Nov 18 10:30:01 fuga4 bluetoothd[634]: Failed to init gatt_example plugin
Nov 18 10:30:01 fuga4 bluetoothd[634]: Bluetooth Management interface initialized
Nov 18 10:30:01 fuga4 bluetoothd[634]: hci0: Load Long Term Keys (0x0013) failed: Not Supported (0x0c)
Nov 18 10:30:02 fuga4 bluetoothd[634]: Adapter /org/bluez/634/hci0 has been enabled
Nov 18 10:30:09 fuga4 gnome-session[1280]: WARNING: Could not parse desktop file blueman.desktop or it references a not found TryExec binary
Nov 18 10:30:09 fuga4 bluetoothd[634]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/HFPAG
Nov 18 10:30:09 fuga4 bluetoothd[634]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/HFPHS
Nov 18 10:30:09 fuga4 bluetoothd[634]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSource
Nov 18 10:30:09 fuga4 bluetoothd[634]: Endpoint registered: sender=:1.40 path=/MediaEndpoint/A2DPSink
Nov 18 10:30:21 fuga4 bluetoothd[634]: Discovery session 0xb8186538 with :1.55 activated
Nov 18 10:32:45 fuga4 bluetoothd[634]: Discovery session 0xb8186538 with :1.65 activated
Nov 18 10:32:48 fuga4 bluetoothd[634]: hci0: Confirm Name (0x0025) failed: Invalid Parameters (0x0d)
Nov 18 10:32:56 fuga4 bluetoothd[634]: Stopping discovery
Nov 18 10:33:01 fuga4 bluetoothd[634]: hci0: Cancel Pair Device (0x001a) failed: Invalid Parameters (0x0d)
john@fuga4:/var/log$ cd /lib/firmware
john@fuga4:/lib/firmware$ sudo pactl load-module module-bluetooth-discover
[sudo] password for john:
Failure: Module initialization failed

hi,

got the same bug, bluetooth doesn't connect to my jbl pulse (wireless bluetooth speaker). However the command given works

pactl load-module module-bluetooth-discover

It needs to be launched at each reboot into terminal. my work around is the following:

a create a sh script blueauto

[code]
#!/bin/sh
sleep 15
pactl load-module module-bluetooth-discover
[/code]

in terminal ==> chmod a+r /to/your/folder/blueauto

and then go to your startup application (controle center) and select the script.
it doesn't connect automaticaly, you need to connect it. but this is a workaround till blueman developer solved this bug.

For my Ubuntu 14.04, [CODE] pactl load-module module-bluetooth-discover [/CODE] returns 'Failure: Module initialization failed' in Terminal. I'm still using default bluez rather than blueman.

As a comparison, Lubuntu 14.04 using Blueman and ath9k is able to pair, connect and stream audio using A2DP. On a diferrent notebook, Ubuntu 14.04 using the default bluetooth application (is it gnome-bluetooth now or bluez?) and iwlwifi only occasionally pairs with the same headset and never streams audio. With Blueman installed, it still does not want to connect and stream audio using Blueman instead.of the default.

Perhaps a knowledgeable comparison between the two (Ubuntu vs Lubuntu) would be enlightening?

Same issue with Ubuntu 14.04 and Denon DHT-T100.
The two systems pair correctly, but no sound.

After following instructions from comment #92, and rebooting, it worked. I can see the ne Sound Output hardware on the sound configuration panel.

Thank you, cschramm.

Nacho

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

I have same problem with bluetooth keyboard. Dunno if it is related but there is no path /org/bluez/*/hci0 in my system

$ bluez-test-manager &
Default adapter is now at path /org/bluez/566/hci0

$ cd /org
bash: cd: /org: No such file or directory

$ bluez-test-adapter list
 [ /org/bluez/566/hci0 ]
    Name = z-0
    Powered = 1
    Devices = dbus.Array([dbus.ObjectPath('/org/bluez/566/hci0/dev_00_18_AC_38_94_32')], signature=dbus.Signature('o'), variant_level=1)
    DiscoverableTimeout = 0
    PairableTimeout = 0
    Discoverable = 0
    Address = C4:85:08:3C:0E:8C
    Discovering = 0
    Pairable = 1
    Class = 0x000000
    UUIDs = dbus.Array([dbus.String(u'00001000-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001001-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000112d-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001112-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000111f-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000111e-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000110c-0000-1000-8000-00805f9b34fb'), dbus.String(u'0000110e-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001105-0000-1000-8000-00805f9b34fb'), dbus.String(u'00001106-0000-1000-8000-00805f9b34fb')], signature=dbus.Signature('s'), variant_level=1)

Just bought a BT soundbase base (Target brand, generic). Am running Ubuntu 14.04, and can confirm these issues for my part as well. Also can confirm that entering the comment "pactl load-module module-bluetooth-discover" fixes the problem for me, albeit not necessarily permanently. I have been mucking around with both the default bluetooth manager and blueman, so no idea if blueman did something else that helped.

Running `gksudo pactl load-module module-bluetooth-discover` gets the device working. Found it at the following URL:

http://askubuntu.com/questions/475817/pulseaudio-unable-to-detect-bluetooth-headset

Would really like this fixed. It's obvious that the drivers are there, but the OS itself is messing something up.

Add me to the list of those effected. I have to go through quite the rigamarole to get it working

1) in terminal sudo pactl load-module module-bluetooth-discover
2) blueman- setup, choose A2DP
3) PAVU- select A2DP
4) Then I select the device with the volume/sound settings.

14.04 with all the latest updates. I hope this issue can be addressed. Thanks!

Have exactly the same issue like poster has.

Working solution:
http://askubuntu.com/a/391720/57122

I'm having the same problem with a Bose Soundlink III and msi laptop with ubuntu 14.04 64 bit. I can confirm that a working solution is(as reported above): http://askubuntu.com/a/391720/57122.
I think that my problem was the absence of pavucontrol package. After its installation and rebooting the machine the bluetooth connection works well (I have only to put manually as main audio peripheral the soundlink III in the audio control panel).
I hope this helps.

Same issue dell E5530 Ubuntu 14.04.1 LTS

instructions on #138 work for me also

things are a little better for me on vivid. my 2 headsets both pair, will set as Headset Service, show up in pavucontrol, and even work with gmail(via firefox via google chat plugin)!

still not working: bose soundlink iii will pair, and even work via ~/.asoundrc, but will not show up pavucontrol.

also not working: neither linphone, sflphone, nor ekiga can find my headsets.

i should mention in /etc/bluetooth/audio.conf after [General] i needed to insert:
Enable=Socket

Hi, I managed to "workaround" this issue by following Mattia Belluco's workaround by the following Debian bug report message:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725610#89

```
More specifically to make a bluetooth headset work in A2DP mode I had to
change settings in audio.conf:

SCORouting=PCM

and keep sure Socket stay disabled.

Once you've done that you would still get a "Stream setup failed error"
unless you manually load module-bluetooth-discover with:

$ pactl load-module module-bluetooth-discover

If the module was not loaded you'll get a number as exit code and that
being the case your next connection attempt should succeed.

I hope that helps.
```

Hello!

We fixed this in Linux Lite months ago. What you folks need is the latest version of blueman from the PPA.

More details here:

https://www.linuxliteos.com/forums/index.php?topic=558.msg8864#msg8864

Hope this helps; works for me...

73 DE N4RPS
Rob

I find this workaround:

cb@cb-AO725:~$ sudo /etc/init.d/bluetooth restart
[sudo] password for cb:
 * Stopping bluetooth [ OK ]
 * Starting bluetooth [ OK ]
cb@cb-AO725:~$ pulseaudio -k
cb@cb-AO725:~$ pulseaudio --start

But it's working only sometime !

The only thing working seems to be the fix in #29... Anything else so far?

Hi everyone
We al have faced the same problem with Bluetooth not connecting. Managed to fix the issue, this way:
1.You need root permissions
2. Go to Computer/etc/bluetooth/audio.conf and open as a root via terminal or GUI.
Add to - [General]
Enable = Sink
Enable= Source
Enable=Gateway

Remove the # before :
1.Disable=Gateway,Source,Socket
2.AutoConnect=true
3.[Headset]
4.[HFP=true
5.[A2DP]
   SBCSources=1
   MPEG12Sources=0

hello

this helped me out.

sudo apt-get purge pulseaudio-module-bluetooth bluetooth bluez-* bluez
sudo apt-get install blueman bluez pulseaudio-module-bluetooth --install-suggests
pactl load-module module-bluetooth-discover

found here -> http://firstdoit.com/quick-tip-bluetooth-a2dp-on-linux-mint-17-qiana-mate/?utm_source=blog.gadr.me

but works on Ubuntu 14.04 perfect (for me) .. good luck

After reading a lot of bug reports and trying several solutions which helped other people (for example #149), but I am still stuck getting Ubuntu 14.04 to work with Bose Soundlink Headphones. Host is a Lenovo Carbon X1 Carbon 3rd gen - having an Intel 7265 card.

I am able to pair, and also can set the A2DP profile for this device. After a couple of seconds however, the device disconnects and kernel log has a couple of

[ 50.181581] Bluetooth: hci0 SCO packet for unknown connection handle 0

lines. Afterwards, the device rejects re-connection, only re-pairing will bring it back to a connected state.

The device works fine with other hosts like several Android phones and tablets, a MacBookAir running OS X, but I also got it running with the same laptop (!) running Ubuntu 15.04. However, for my work I need to stick with 14.04 to be compatible with colleagues.

Suspected a bug in the firmware, but I couldn't found newer firmware than the one already used:

[ 760.815953] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 760.895882] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated

Tried several kernel versions, no luck either.

Anyone with a idea how to fix the "SCO packet for unknown connection handle" problem?

Sorry for self-replying.. after another hour, I applied #15, deleted the pairing, used blueman to re-pair and now it works :). Finally :) Thanks everyone for the nice thread.

Currently, on Lubuntu Trusty, I have no problems with Skullcandy Hesh 2 and:
 * kernel 3.13.0-63-generic #103
 * pulseaudio 1:4.0-0ubuntu11.1+kxstudio1 (I did not test with the standard Canonical version, sorry)
 * bluez 4.101-0ubuntu13.1
 * blueman 1.23-git201403102151-1ubuntu

though I will note it's not always as seamless as I would like. I've discovered elsewhere people suggesting that the adapter is turned on after pulse does its check for bluetooth adapters. That leaves you two choices:
 1. pactl load-module module-bluetooth-discover && pulseaudio -k (note actually sending a KILL signal to the daemon may get it unstuck if it's not behaving)
 2. remove the conditional from /etc/pulse/default.pa regarding loading module-bluetooth-discover
neither of which are particularly elegant, but oh well.

This and similar issues are ultimately an aesthetic issue, though, and deserve a separate bug report, as this more general one has brown extensive enough. From my experience, audio sink service (A2DP) *IS* possible with current versions.

I'm inclined to call this fixed, unless I hear otherwise from folks.

I have two notebook computers - a Toshiba and a Fujitsu both of which are very old and are both dual boot computers with Windows 7 and Ubuntu 14.04 LTE 32 bit. Both computers and both operating systems work fine with Bluetooth linking to a Bose mini soundlink speaker for playing music. I use a USB bluetooth dongle for the link and all works well.

However, with a much newer laptop, a Toshiba Satellite Pro C50-A-1K9 running the 64 bit version of Ubuntu 14.04 LTE I cannot get bluetooth to work despite using the same dongle and the same speaker. The first time it finds the device, attempts to pair, but asks that a particular 4 digit code be entered from the device. This is of course impossible as the Bose mini soundlink speaker does not have a keypad! Further attempts to search for bluetooth devices after this first time find nothing. If I then go back to the old notepad computers they also cannot find the device at all with either Windows or Ubuntu 14.04 32 bit. I strongly suspect that the 64 bit version of Ubuntu 14.04 LTE has sent a code to the speaker which prevents it linking via bluetooth thereafter.

If anyone else has the Bose mini soundlink speaker and needs to overcome this problem, then

Perform a factory reset on the speaker by first turning it on then holding down the bluetooth button for about ten seconds when the speaker beeps and will now work again with the old computers and windows 7 or Ubuntu 14.04 LTE 32 bit.

Hope a skilled programmer finds the bug!

I've applied all the fixes that folks have recommended; I still need to do the workaround from comment #29

{QUOTE] Test by:
pactl list | grep -i module-bluetooth-discover

If empty load via
 pactl load-module module-bluetooth-discover [/QUOTE]

Just think, in 4 more months Ubuntu 14.04 will be EOL and this will still be an open bug! So much for the much-vaunted LTS releases...

This is far from fixed IMO.

I experienced the exact same issue as in the description. My problem seemed to be caused by the system auto-logging into the guest account on boot. After I disabled that feature the issue was resolved for my main account

The same problem for me,I can't change my sound quality in my JBL Extreme speaker :/

+1

I have got this bug. If you need some debug information, I can provide it.

Buggy bluetooth has been around since 15.04 when I had devices to connect. I experience similar problems as many others that the connection is full of bug and pray. It is time it change!

I am using Ubuntu 16.04, XUbuntu 16.04 and Ubuntu 15.04.

Let me know if I can contribute with log reports etc.

After upgrade from ubuntu 14.04 to 16.04 can not switch from A2DP to HSP in gnome-control-center sound.

Same problem in 16.04 on Dell 5510 Precision workstation.

Bose Soundlink (Tangent-BT) gets paired, but does not show in control panel as output option.
Bose Mini Soundlink gets paired, but does not show as output option.

However, Jawbone Big Jambox gets paired, AND shows up as "headset" output option. But sounds distorted and volume ramps up and down again at times.

I've got problem with Jabra Rox Wireless in pairing mode hangs up ubuntu 16.04(current) also same problem on previously installed 14.04. What info I can provide to help to investigate this ?

I am Affected Too! I bought a Headset it aint working. got it working once or twice with a lot of work as far as I can tell it sometimes it works and sometimes doesn't with those workarounds described here. I haven't found a permanent solution for the Problem though. pairing process works fine. but my headset doesn't show up in pulseaudio.

what an ordeal to get a bluetooth headset working in 16.04, way worse than 14.04 was (at least in 14.04 it only would not keep the output profile and had to select the headset output on every re-connection)

I have a Voyager Legend that will pair but not function. This device shows up initially as headset unit (mono) but selecting it does not work. I have to restart the bluetooth service, kill pulseaudio, then sometimes it will start working in HSP. Then I change it to A2DP mode and it stops working (I can not select it as output anymore, when I change it to A2Dp it jumps from the headse to the first output, selecting headset again it is back in HSP). I have to restart bluetooth again and kill pulseaudio again then I can select it and change to A2DP finally and it keeps and works perfectly... until I disconnect the headset walking away or turn it off.

when I turn it back on again I get no output. looking at logs I see

[pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.

any attempt to play audio this error appears. Doing all the "tricks" above ALSO does nothing to fix the sink issue. I have to now change the profile from A2DP back to HSP, then click test a few times and the headset connects, but I can not change it to A2DP again as it jumps up to top output again.

Now at this point I have to do all of the first tricks again (kill pulse, restart blue, etc) and then SOMETIMES I can select A2DP again and it will work again, but many times I have to do this 2 or more times before it will finally work

On a side note at least I was able to use my headset on 14.04 with both my computer and my cell phone at the same time, now that is impossible as it never works if the phone is connected

I've the same or similar issue with 16.04,

When i turn on my Headset and connect via Bluetooth, it starts with different Profiles depending on the previous status:

If I've previously used A2DP it will starts with off
If I've used HSP or switched back to it before turning the headset off, it starts with HSP

Workaround:

If It starts with Off, i can't select A2DP it always jumps back, but if I select HSP manually, turn the Headset off and on again it will now start with Profile HSP and I'm now able to select A2DP, if I switch back to the HSP Profile, before turning my Headset off / disconnecting it, it will also work the next start, if I stay on the A2DP Profile before turning off / disconnecting, I've to redo the Workaround steps from beginning.

It looks like the driver (or whatever) can't handle to start with A2DP Profile. It was really painfull until I've read about the workaround in another forum, it is still annoying but at least i don't need to restart any services or make a reboot

Hey,

@all this is to inform that we are aware of these issues and will be investing time into improving the headsets experience.

Same for me, my new bluetooth speaker is paired but I can't stream the audio to it.
Someone posted a fix for this (worked for me and other people) at askubuntu here (first answer) : http://askubuntu.com/questions/689281/pulseaudio-can-not-load-bluetooth-module-15-10-16-04-16-10

seems pulseausio / X11 related

The Bluetooth device works as an audio output device just fine in the live session. Perhaps this is broken by some update? I tried downgrading all PulseAudio-related packages to the original release versions, but no luck.

Re comment #167: The fix does not work for me (Ubuntu GNOME 16.10).

I got a bluetoothd crash, but I cannot get apport to report it (nothing happens if I select the option to send an error report). I have saved the .crash file and can attach it here if required.

Bluetooth audio works on KDE (Kubuntu). If KDE (kubuntu-desktop) is installed alongside GNOME, it works on GNOME as well(!).

Sorry for the comments above, it was my mistake. The fix reported about in comment #167 does indeed work.

Hello Fabien, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Verified. Using the proposed packages my bluetooth audio device is no longer randomly unselectable.

Can we get an update for Zesty?

Zesty already contains the latest release (and all fixes):
https://launchpad.net/ubuntu/+source/pulseaudio

So if you have a problem with zesty, please log a new bug.

Even after applying all updates on Ubuntu GNOME 17.04, my Bluetooth audio device doesn't show up in the Sound settings. The workaround mentioned in comment #167 still works.

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.3

---------------
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.

 -- Daniel van Vugt <email address hidden> Tue, 23 May 2017 16:24:14 +0800

The verification of the Stable Release Update for pulseaudio has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

I closed the gnome-bluetooth part of this bug since this was apparently fixed in pulseaudio instead.