desktop-packages team mailing list archive

[Sergio Costas <rastersoft@xxxxxxxxx>]

Hi all:

I have exactly the same problem as everyone, and tried everything
commented here without success. But I found a way of doing it work,
which maybe helps to fix the error:

* Paired my headset, but didn't set it as trusted. Restarted the bluetooth service (did this only once, not every time I want to connect your headset; is just to set it in a know state).
* Now, every time I want to use the headset, I turn it on. Bluetooth icon in gnome will briefly show as connected, but returns to disconnected (because it detected the paired device, but, as it is not a trusted one, will no connect automatically to it).
* Wait about ten seconds until I hear a little "pop" in my headset (I suspect it is when, after waiting a connection, it puts in some kind of sleep mode to save battery)
* Now I can go to the bluetooth icon and set A2DP mode, and everything works fine.

If I try to connect it before that status change, the headset will stuck
in HSP/HFP mode and will refuse to change to A2DP mode.

But there is a case when this fails: sometimes, when turning on the
headset, Gnome shell shows a popup and asks me if I want to accept the
connection. In that case, no matter if I accept or deny it, waiting to
hear the "pop" doesn't work: it will also remain stuck in HSP/HFP mode.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1181106

Title:
  Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and
  14.04 (trusty)

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the device in the "Play sound through" listing in the Sound system control panel, but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions