"Stream Setup Failed" error when connecting to speaker
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-git2014031
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/
Connect 00:1D:DF:EA:EC:A4 org.bluez.AudioSink
_________
init_services (/usr/lib/
Loading services
_________
__init__ (/usr/lib/
caching initial properties
_________
notify (/usr/lib/
<Device object at 0xb519ca08 (blueman+
_________
__del__ (/usr/lib/
deleting device /org/bluez/
_________
Destroy (/usr/lib/
invalidating device /org/bluez/
_________
initialize (/usr/lib/
rebuilding menu
_________
__init__ (/usr/lib/
caching initial properties
_________
__del__ (/usr/lib/
deleting device /org/bluez/
_________
Destroy (/usr/lib/
invalidating device /org/bluez/
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.
Remove Blueman bluetooth- discover
apt-get purge blueman
sudo pactl load-module module-
Then delete the pairing, pair with the device again and see if it appears in sound settings