Control: reassign -1 bluez/4.101-4.1 Control: retitle -1 bluez: cannot connect without Socket interface
Hi Adrian, On Sat, Apr 26, 2014 at 3:00 AM, Adrian Immanuel Kieß <adr...@kiess.at> wrote: > With Socket=Disabled bluez reports "Stream setup failed" and /var/log/syslog > reports: > > Apr 26 07:56:42 g6 bluetoothd[9106]: bluetoothd[9106]: Unable to select SEP > Apr 26 07:56:42 g6 bluetoothd[9106]: Unable to select SEP > Apr 26 07:56:42 g6 kernel: [ 876.200899] input: 00:1D:DF:D5:E3:2E as > /devices/virtual/input/input20 > Apr 26 07:56:43 g6 acpid: input device has been disconnected, fd 15 > > This also does not work. > > I tried with two bluetooth USB sticks; an Trust v2 bluetooth and an Ultron > v4 bluetooth stick. I'm sorry I cannot provide more help but it looks like the problem is not with pulseaudio but in bluez. There are some possible workarounds for your problem here: http://askubuntu.com/questions/287254/ubuntu-13-04-bluetooth-a2dp-does-not-work You might want to try them, please report back if they work. Dear bluez Maintainers, the problem is as follows: According to [1] and [2], enabling the Socket interface in audio.conf breaks AD2P selection by pulseaudio. Unfortunately, some devices do not work with the socket interface disabled (such as the OPs and [3]). [1] http://lists.freedesktop.org/archives/pulseaudio-discuss/2012-November/015464.html [2] https://bugzilla.redhat.com/show_bug.cgi?id=964031 [3] https://bugzilla.redhat.com/show_bug.cgi?id=969856 -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
