Dear Maintainer, After pairing the 'Creative T30 Wireless' bluetooth speakers with my notebook I never had any problems connecting them, but in most cases they won't appear in GNOME audio settings (or pavucontrol) as audio output device. Over the last months I used to disconnect them, switch bluetooth off and on again and then connect the speakers again – after some attempts the speakers appeared in GNOME audio settings and I was able to use them. Yesterday I realized that it seems to work immediately if I restart bluetoothd before I try to connect the speakers. I'll attach three log files: - dmesg output At the end you can see that I connected my speakers three times (00:02:3C:49:93:08) until I was able to use them - pulseaudio-log1 Here I started pulseaudio, entered GNOME bluetooth settings, connected to my bluetooth speakers and then entered GNOME audio settings. In this case the speakers were not added as audio output device. - pulseaudio-log2 Here I started pulseaudio, entered GNOME bluetooth settings, connected to my bluetooth speakers and then entered GNOME audio settings. This time the speakers were addded as audio output device. Please tell me if I can provide any more useful information.
I'll add a bluetoothd log file to this report. I started the Bluetooth daemon, entered GNOME bluetooth settings, connected to my bluetooth speakers and then entered GNOME audio settings. The speakers were not added as audio output device. This turned out to be a bad shot. Sometimes it works after restarting bluetoothd, sometimes it doesn't.
After finding a related bug report [1] (reported against bluez) I tried to connect the speakers after boot several times (around 20 attempts with two different notebooks). Before that I didn't realize that I _always_ have to restart bluetoothd (or deactivate and reactivate the bluetooth adapter) so that the speakers are added as output device when I connect them… So now I can confirm that. This report is probably a duplicate of #772717. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772717
Control: reassign -1 bluez Control: forcemerge 772717 -1 I'm sorry for the late reply. I'm afraid I cannot help much in the bluetooth side of things. I'm thus merging this bug with the one you quoted.
Because I was affected by a Wi-Fi Bluetooth coexistence bug (when I use bluetooth speakers for audio output Wi-Fi stops working, see bug #777759), I disabled iwlwifi module option bt_coex. After disabling bt_coex the behavior when I connect my bluetooth speakers changed significantly: most of the time it just works (they appear in GNOME audio settings as audio output device). Sometimes the first connection after boot fails – the speakers are connected but disconnect after about 5-10 seconds. When I try it again, the connection persists and the speakers appear in GNOME audio settings as audio output device. I have to test this some more but it seems to me that this could be a kernel bug.
After testing this for two months now I just wanted to mention that I was wrong (see my last comment): I had the iwlwifi module option bt_coex disabled all the time but I was and I am still affected by this bug (same behavior as originally reported).