FS#37236 - After Gnome stack update bluetooth headphones doesn't connect

Attached to Project: Arch Linux
Opened by Simonas (nagi) - Monday, 07 October 2013, 20:13 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 03 November 2013, 14:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After gnome stack update connecting bluetooth headphones fails with following message:

Oct 07 22:49:14 bluetoothd[314]: Unable to select SEP

It is presumably because bluez was updated to version 5.something and pulseaudio is built with bluez4 support.

Additional info:
* package version(s) bluez 5.9-1, bluez-libs 5.9-1, pulseaudio 4.0-2
* config and/or log files etc.

Default config for packages mentioned above


Steps to reproduce:
Try connecting bluetooth headphones after updating to GNOME 3.10 stack.
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 03 November 2013, 14:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  Reported fixed with pulseaudio 4.0-6
Comment by Felix (nobodynhio) - Monday, 07 October 2013, 23:07 GMT
Same here. Autoconnect after Startup gives following verbose info in bluetoothctl:

---
[NEW] Device xx:xx:xx:xx:xx:xx Philips SHB9100
[CHG] Device xx:xx:xx:xx:xx:xx Connected: yes
[CHG] Device xx:xx:xx:xx:xx:xx UUIDs has unsupported type
[CHG] Device xx:xx:xx:xx:xx:xx Connected: no
---

The Autoconnect has definitely worked until i upgraded to gnome 3.1 and new cinnnamon (forcing upgrade to bluez5)

Trying to manually connect in bluetoothctl, with "connect xx:xx:xx:xx:xx:xx"

---
[CHG] Device xx:xx:xx:xx:xx:xx Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device xx:xx:xx:xx:xx:xx Connected: no
Comment by Simonas (nagi) - Tuesday, 08 October 2013, 06:22 GMT
For me using `pulseaudio-git` from AUR fixes the issue. I just modified its PKGBUILD to add --enable-bluez flag to configure. Maybe backporting patches enabling bluez5 support would be a smart move.
Comment by Felix (nobodynhio) - Tuesday, 08 October 2013, 08:18 GMT
Or updating pulseaudio in repo.. Thx a lot for the hint, already tried installing git but without --enable-bluez.
Comment by Michael Trunner (trunneml) - Monday, 14 October 2013, 11:42 GMT
Same here. Connecting my bluetooth headphones fails with "Unable to select SEP".
Comment by Sven-Ola Tuecke (sven-ola) - Sunday, 27 October 2013, 16:13 GMT
Same here. pulseaudio-git does not have --enable-bluez any more and should find out --enable-bluez5 automatically, check with "grep -r HAVE_BLUEZ_5 src/pulseaudio/Makefile" after building. While "bluetoothctl" now connects the headset, sadly gnome audio settings is broken now. Clicking on the audio icons now shows:

[sven-ola@pcexo ~]$ gnome-control-center
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

Speicherzugriffsfehler (Speicherabzug geschrieben)

Edit: after rebooting, gnome desktop does not start. Tried to recompile ABS/extra/pulseaudio, which has a dependancy to bluez4 -> bluez. No BT connect anyhow. Checked the pulseaudio git log. Seems bluez-5 support is not released yet, lot of changes. Next pulseaudio release may need some gnome changes also or at least a recompile. Sigh. I reverted, since a BT headset isn't worth the trouble.
Comment by Sven-Ola Tuecke (sven-ola) - Wednesday, 30 October 2013, 07:22 GMT
AFACIT now, the oops with pulseaudio-git and gnome-control-center is the same thing as in https://bugs.archlinux.org/task/37528 because in the meantime stock pulseaudio+libpulse got an update 4.0.2->4.0.5 with the same oops. Currently preparing a gdb stack trace and will attach to https://bugs.archlinux.org/task/37528

Loading...