Bug 79213 - Paired bluetooth a2dp does not connect to audio sink
Summary: Paired bluetooth a2dp does not connect to audio sink
Status: RESOLVED NOTOURBUG
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: modules (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-25 14:46 UTC by quentin.denis
Modified: 2015-09-13 19:43 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
daemon vvvv output (172.83 KB, text/plain)
2014-05-25 14:46 UTC, quentin.denis
Details

Description quentin.denis 2014-05-25 14:46:36 UTC
Created attachment 99774 [details]
daemon vvvv output

My bluetooth device pairs successfully but won't connect to pulseaudio:
BLUETOOTH:
pairing is successful (according to 'bluethoothctl info') but connection fails: 
[bluetooth]# connect 00:1D:DF:E4:7D:88
Attempting to connect to 00:1D:DF:E4:7D:88
Failed to connect: org.bluez.Error.Failed
Reason (systemctl status bluetooth):
May 17 23:55:22 linux-v3k0.site bluetoothd[4391]: connect error: Invalid
exchange (52)

PULSEAUDIO:
See attached log from pulseaudio -vvvv, especially:
[pulseaudio] bluez5-util.c: Properties changed in adapter /org/bluez/hci0
Nothing more happens and pavucontrol won't show a new output device.

I am running openSUSE 13.1 with pulseaudio 5:
quentin@linux-v3k0:~> rpm -qa|grep pulseaudio
pulseaudio-module-bluetooth-5.0-2.2.i586
pulseaudio-5.0-2.2.i586
pulseaudio-module-jack-5.0-2.2.i586
pulseaudio-module-x11-5.0-2.2.i586
pulseaudio-utils-5.0-2.2.i586
pulseaudio-module-zeroconf-5.0-2.2.i586
pulseaudio-module-gconf-5.0-2.2.i586
pulseaudio-module-lirc-5.0-2.2.i586
Comment 1 Tanu Kaskinen 2014-05-27 06:38:30 UTC
I don't think this is a PulseAudio bug. PulseAudio is not involved when connecting the device. You should report this to the BlueZ folks.

(I probably suffer from the same bug, btw. If I want to use my headset, I need to unpair it first, then after re-pairing connecting it works for one time.)
Comment 2 quentin.denis 2014-06-05 09:12:20 UTC
I have further investigated the issue and it is indeed a bluetooth-related problem. Somehow the PIN is not handled correctly by bluedevil and I have to pair my device manually. Thanks you.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.