"Stream Setup Failed" error when connecting to speaker

Bug #1493709 reported by Ray Peterson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
New
Undecided
Unassigned
bluez (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu Version: Ubuntu 14.04.3 LTS
Package Version: 1.23-git201403102151-1ubuntu1 (Tried several other versions too)

I've looked at a bunch of tutorials, but I just can't solve this problem. In fact, I've never seen Bluetooth audio work, for anyone I know, granted most of them are using a Raspberry Pi.

Anyway, first of all let me just say that I'm defiantly somewhat of a "Linux Noob", so I honestly have no idea what's going on around here, but I heard this is the official website of this and many other Linux packages, so I'm here to report a bluetooth audio bug.

Every time I try to connect my Bluetooth speaker to my Linux computer (Well, in this specific case it's a single-board ARM PC, which looks suspiciously similar to the Pi 2. Coincidence?), it connects for about a second and then drops the connection. It never shows up in PulseAudio either. Sometimes, it will stay paired with the computer and the pair light will stay solid like it's connected, but when I try to connect it to the "Audio Sink" service, blueman crashes! Okay, well not really crashes, but the window just closes for no reason, even though the tray icon is still responsive.

Bottom line is, the speaker never connects to the Bluetooth audio service. I would tell you the model of the speaker, but I've actually tried a whole bunch of different speakers and headsets. (Don't ask me why I have so many Bluetooth speakers.) But they all lead to the same result of connecting for a second, until blueman gives a "Stream Setup Failed" error. Once, I actually closed blueman-applet and ran it from the terminal, to see if it was printing an error or something. Here is the relevant output from pairing to my JBL Charge:

_________
on_item_activated (/usr/lib/python2.7/dist-packages/blueman/plugins/applet/RecentConns.py:279)
Connect 00:1D:DF:EA:EC:A4 org.bluez.AudioSink
_________
init_services (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:73)
Loading services
_________
__init__ (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:16)
caching initial properties
_________
notify (/usr/lib/python2.7/dist-packages/blueman/plugins/applet/RecentConns.py:237)
<Device object at 0xb519ca08 (blueman+main+Device+Device at 0x4f9cd0)> org.bluez.AudioSink dbus.Array([], signature=None)
_________
__del__ (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:60)
deleting device /org/bluez/504/hci0/dev_00_1D_DF_EA_EC_A4
_________
Destroy (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:95)
invalidating device /org/bluez/504/hci0/dev_00_1D_DF_EA_EC_A4
_________
initialize (/usr/lib/python2.7/dist-packages/blueman/plugins/applet/RecentConns.py:136)
rebuilding menu
_________
__init__ (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:16)
caching initial properties
_________
__del__ (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:60)
deleting device /org/bluez/504/hci0/dev_00_1D_DF_EA_EC_A4
_________
Destroy (/usr/lib/python2.7/dist-packages/blueman/main/Device.py:95)
invalidating device /org/bluez/504/hci0/dev_00_1D_DF_EA_EC_A4

So, is this a bug (probably), and if so, is anyone going to fix it? Honestly, I'm not entirely sure if this is actually a bug with blueman, maybe it's a bug with bluez or something, I sure wouldn't know.

Revision history for this message
Jeremy (wa113y3s) wrote :

Remove Blueman
apt-get purge blueman
sudo pactl load-module module-bluetooth-discover

Then delete the pairing, pair with the device again and see if it appears in sound settings

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.