+++ This bug was initially created as a clone of Bug #1124996 +++ +++ This bug was initially created as a clone of Bug #981355 +++ Description of problem: I have a CREATIVE S2 Wireless speaker system. It was working fine using Fedora 17 and any player. Now I have upgraded to Fedora 19, I can search and pair the speaker system without any problems. But, when I select this Output device in the Sound Settings, it does not work. Not even the test speaker function. Thank you Version-Release number of selected component: gnome-abrt-0.2.12 Additional info: reporter: libreport-2.1.5 kernel: 3.9.8-300.fc19.x86_64 libpeerconnection.log: type: libreport --- Additional comment from Ned Forrester on 2013-08-21 23:54:47 EDT --- I have the same symptoms: headset pairs OK, appears in Gnome Sound Settings, and in Pulseaudio Volume Control. There is a slight hissing noise, the volume of which responds to the volume slider in Pulseaudio Volume Control. However, no audio ever heard from any source, even from the Gnome speaker test. I last had this headset working on a different machince running FC12. I have been unable to get it work on my new machine under either FC17 or FC19. System: Lenovo T530 Fedora 19: 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux alsa-firmware-1.0.27-1.fc19.noarch alsa-lib-1.0.27.2-1.fc19.x86_64 alsamixergui-0.9.0-0.14.rc2.fc19.x86_64 alsa-oss-1.0.17-8.fc19.x86_64 alsa-oss-libs-1.0.17-8.fc19.x86_64 alsa-plugins-oss-1.0.27-1.fc19.x86_64 alsa-plugins-pulseaudio-1.0.27-1.fc19.x86_64 alsa-tools-firmware-1.0.27-2.fc19.x86_64 alsa-utils-1.0.27.2-2.fc19.x86_64 bluez-4.101-9.fc19.x86_64 bluez-alsa-4.101-9.fc19.x86_64 bluez-compat-4.101-9.fc19.x86_64 bluez-cups-4.101-9.fc19.x86_64 bluez-gstreamer-4.101-9.fc19.x86_64 bluez-hcidump-2.5-2.fc19.x86_64 bluez-hid2hci-4.101-9.fc19.x86_64 bluez-libs-4.101-9.fc19.x86_64 pulseaudio-3.0-10.fc19.x86_64 pulseaudio-esound-compat-3.0-10.fc19.x86_64 pulseaudio-libs-3.0-10.fc19.x86_64 pulseaudio-libs-glib2-3.0-10.fc19.x86_64 pulseaudio-module-bluetooth-3.0-10.fc19.x86_64 pulseaudio-module-gconf-3.0-10.fc19.x86_64 pulseaudio-module-jack-3.0-10.fc19.x86_64 pulseaudio-module-x11-3.0-10.fc19.x86_64 pulseaudio-utils-3.0-10.fc19.x86_64 pulsecaster-0.1.9-3.fc19.noarch Device: Jabra BT500 -- pactl list sinks Sink #0 State: RUNNING Name: alsa_output.pci-0000_00_1b.0.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 4 Mute: no Volume: 0: 100% 1: 100% 0: 0.00 dB 1: 0.00 dB balance 0.00 Base Volume: 100% 0.00 dB Monitor Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor Latency: 19693 usec, configured 20000 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC269VC Analog" alsa.id = "ALC269VC Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf3a30000 irq 48" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1e20" device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "352800" device.buffering.fragment_size = "176400" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" alsa.mixer_name = "Realtek ALC269VC" alsa.components = "HDA:10ec0269,17aa21f6,00100203" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Ports: analog-output-speaker: Speakers (priority: 10000, not available) analog-output-headphones: Headphones (priority: 9000, available) Active Port: analog-output-headphones Formats: pcm Sink #1 State: IDLE Name: combined Description: Simultaneous output to Built-in Audio Analog Stereo, Jabra BT500 Driver: module-combine-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 11 Mute: no Volume: 0: 80% 1: 80% 0: -5.85 dB 1: -5.85 dB balance 0.00 Base Volume: 100% 0.00 dB Monitor Source: combined.monitor Latency: 437109 usec, configured 128000 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.class = "filter" device.description = "Simultaneous output to Built-in Audio Analog Stereo, Jabra BT500" device.icon_name = "audio-card" Formats: pcm Sink #15 State: RUNNING Name: bluez_sink.00_16_8F_08_5C_99 Description: Jabra BT500 Driver: module-bluetooth-device.c Sample Specification: s16le 1ch 8000Hz Channel Map: mono Owner Module: 51 Mute: no Volume: 0: 100% balance 0.00 Base Volume: 100% Monitor Source: bluez_sink.00_16_8F_08_5C_99.monitor Latency: 134000 usec, configured 128000 usec Flags: HARDWARE HW_VOLUME_CTRL LATENCY Properties: bluetooth.protocol = "hsp" device.intended_roles = "phone" device.description = "Jabra BT500" device.string = "00:16:8F:08:5C:99" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" bluez.path = "/org/bluez/675/hci0/dev_00_16_8F_08_5C_99" bluez.class = "0x20040c" bluez.name = "Jabra BT500" device.icon_name = "audio-card-bluetooth" Ports: bluetooth-output: Bluetooth Output (priority: 2000, available) Active Port: bluetooth-output Formats: pcm --- Additional comment from Francisco Grau on 2013-10-21 03:28:22 EDT --- Hi, this problem was resolved more or less for some time. But now there is another problem with the Bluetooth audio. (the audio was working, but the audio preferences dialog will randomly close) Since the Blueman Device Manager has been included, the bluetooth (Creative S2) speakers are not working anymore. The device pairs ok, but when I choose to "Connect to" "Audio Sink" it will connect properly the speakers (the speakers indicator shows that the pairing is working) and then the Blueman Device Manager will say "Connection Failed: Stream setup failed", then it disconnects the speakers and nothing else happens. The Bluetooth device panel from the Gnome settings does the same thing. It pairs, connects for 2 seconds, then disconnects. --- Additional comment from Ned Forrester on 2014-01-14 17:12:04 EST --- Francisco, how was this resolved for you? I still am not able to get bluetooth audio to work under Fedora 19. For me, everything is the same as reported in comment 1, above, except for keeping all packages up-to-date. --- Additional comment from Stuart D Gathman on 2014-02-02 21:25:11 EST --- Same problem with BR-100 audio device - connects, but then gets stream setup failed. All packages up to date. --- Additional comment from Stuart D Gathman on 2014-02-03 12:16:49 EST --- One possible problem, I see that my bluetooth adapter is 2.0, and the BT audio device is 3.0. As I understand it, adapters are backward compatible with older protocols, but devices are not. So it is worth a try to upgrade to a v4.0 adapter. --- Additional comment from Stuart D Gathman on 2014-03-23 19:19:31 EDT --- Upgrading to a 4.0 adapter fixes the problem. 3.0 devices require a 3.0 or newer adapter, and the bluetooth drivers don't seem to be able to detect this problem (it seems like it should be easy - but perhaps there is some braindamage in the protocol where older adapters can't detect newer devices - i.e. the protocol version are not explicit). --- Additional comment from Stuart D Gathman on 2014-05-11 20:54:01 EDT --- Hmm. I added a 4.0 adapter to a computer with a 2.0 adapter on the motherboard. It still hangs with "stream setup failed". Apparently, the mere presence of a 2.0 adapter does the damage. Let me try blacklisting the driver for the 2.0 adapter. --- Additional comment from Stuart D Gathman on 2014-07-17 10:00:48 EDT --- I blacklisted the motherboard 2.0 adapter, and even disabled it in BIOS. The only adapter seen is the USB 4.0 adapter - that I did get to work on an older laptop: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Pairing works, but attempting to connect audio get the dreaded "stream setup failed". --- Additional comment from Stuart D Gathman on 2014-07-28 13:47:49 EDT --- Same problem on Fedora 20, two different laptops. Two different speakers. Bluetooth dongle that worked in F17. --- Additional comment from Stuart D Gathman on 2014-07-29 21:39:38 EDT --- Suddenly (perhaps after some updates, none of which look related), the F19 laptop that was working now gets: Jul 29 21:25:19 silver bluetoothd[775]: bluetoothd[775]: Permission denied (13) Jul 29 21:25:19 silver bluetoothd[775]: Permission denied (13) There are no "denied" entries in audit.log --- Additional comment from Stuart D Gathman on 2014-07-30 15:34:12 EDT --- On F20, here is what appears in journalctl -a when attempting to connect bluetooth audio: Jul 30 14:58:32 elissa.gathman.org gnome-session[1531]: ** Message: has_config_widget 94:23:6E:0B:BD:AF AudioSink Jul 30 14:58:33 elissa.gathman.org gnome-session[1531]: ** Message: has_config_widget 94:23:6E:0B:BD:AF A/V_RemoteControlTarget Jul 30 14:58:33 elissa.gathman.org gnome-session[1531]: ** Message: has_config_widget 94:23:6E:0B:BD:AF A/V_RemoteControl Jul 30 14:58:35 elissa.gathman.org bluetoothd[716]: connect error: Software caused connection abort (103) Jul 30 14:58:45 elissa.gathman.org fprintd[9347]: ** Message: No devices in use, exit Jul 30 14:58:56 elissa.gathman.org bluetoothd[716]: connect error: Connection timed out (110) --- Additional comment from Stuart D Gathman on 2014-07-30 15:38:35 EDT --- pulseaudio-5.0-7.fc20.i686 pulseaudio-module-bluetooth-5.0-7.fc20.i686 On a second attempt, this is what we get: Jul 30 15:00:09 elissa.gathman.org gnome-session[1531]: available 0** Message: has_config_widget 94:23:6E:0B:BD:AF AudioSink Jul 30 15:00:09 elissa.gathman.org gnome-session[1531]: ** Message: has_config_widget 94:23:6E:0B:BD:AF A/V_RemoteControlTarget Jul 30 15:00:09 elissa.gathman.org gnome-session[1531]: ** Message: has_config_widget 94:23:6E:0B:BD:AF A/V_RemoteControl Jul 30 15:00:12 elissa.gathman.org bluetoothd[716]: connect error: Permission denied (13) Jul 30 15:00:14 elissa.gathman.org bluetoothd[716]: connect error: Connection refused (111) Jul 30 15:00:16 elissa.gathman.org bluetoothd[716]: connect error: Connection refused (111) Jul 30 15:00:17 elissa.gathman.org bluetoothd[716]: connect error: Connection refused (111) Jul 30 15:00:19 elissa.gathman.org bluetoothd[716]: connect error: Connection refused (111) --- Additional comment from Stuart D Gathman on 2014-08-05 12:18:55 EDT --- This might be relevant: http://www.spinics.net/lists/linux-bluetooth/msg22729.html Can I just stop the bluetooth.service and manually run bluetoothd? Will try it for some debugging output. --- Additional comment from Stuart D Gathman on 2014-08-05 12:31:21 EDT --- bluetoothd[24803]: src/device.c:connect_profiles() /org/bluez/hci0/dev_94_23_6E_0B_BD_AF (all), client :1.329 bluetoothd[24803]: profiles/audio/a2dp.c:a2dp_sink_connect() path /org/bluez/hci0/dev_94_23_6E_0B_BD_AF bluetoothd[24803]: a2dp-sink profile connect failed for 94:23:6E:0B:BD:AF: Protocol not available According to this random person on the internet, pulseaudio does not support bluez-5, and ALSA does not support bluez-5. And bluez-5 cannot support a2dp without pulseaudio. So this seems to be an integration total failure. :-( According to http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5.0/, the current [pulseaudio] 4.0 release does not support bluez 5, and it seems even 5.0 is not going to support HFP. And I heard ALSA cannot support bluez5 without pulseaudio... --- Additional comment from Stuart D Gathman on 2014-08-05 12:33:11 EDT --- The version combo from he11: pulseaudio-5.0-7.fc20.i686 bluez-5.18-1.fc20.i686 --- Additional comment from Rex Dieter on 2014-08-05 13:50:07 EDT --- Only HSP/HFP modes are not supported (yet), see also bug #1045548 and upstream http://bugs.freedesktop.org/show_bug.cgi?id=73325 --- Additional comment from Stuart D Gathman on 2014-09-08 10:00:07 EDT --- This seems to be fixed now. It is not obvious which update fixed it. --- Additional comment from Stuart D Gathman on 2014-09-16 10:19:51 EDT --- Ok, not quite fixed. 1) bluetooth audio stops working after suspend. A reboot fixes it. 2) with the last set of updates, it doesn't work again. packages that might be relevant: kernel-3.16.2-200.fc20.i686 gstreamer1-libav-1.2.4-2.fc20.i686 Using bluetoothctl (to avoid bugs in the gnome applet - 100% CPU during discovery), this is what now happens after connect (after fresh reboot): [bluetooth]# connect 94:23:6E:0B:BD:AF Attempting to connect to 94:23:6E:0B:BD:AF [CHG] Device 94:23:6E:0B:BD:AF Connected: yes Failed to connect: org.bluez.Error.Failed [CHG] Device 94:23:6E:0B:BD:AF Connected: no [CHG] Device 94:23:6E:0B:BD:AF Connected: yes [CHG] Device 94:23:6E:0B:BD:AF Connected: no [CHG] Device 94:23:6E:0B:BD:AF Connected: yes [CHG] Device 94:23:6E:0B:BD:AF Connected: no [CHG] Device 94:23:6E:0B:BD:AF Connected: yes [CHG] Device 94:23:6E:0B:BD:AF Connected: no [CHG] Device 94:23:6E:0B:BD:AF Connected: yes [CHG] Device 94:23:6E:0B:BD:AF Connected: no ... --- Additional comment from Stuart D Gathman on 2014-09-16 10:21:28 EDT --- --- Additional comment from Rex Dieter on 2014-09-16 10:30:28 EDT --- OK, if suspending is the trigger, that's most likely a driver issue (reassigning to kernel). --- Additional comment from Stuart D Gathman on 2014-09-16 10:33:32 EDT --- Rebooting with previous kernel allows connect to work, so there is definitely a problem with kernel-3.16. However, pulseaudio still doesn't allow an audio connection. So that is broken also by the updates. Pulseaudio itself was not updated, so it is not clear what broke it. Should I open a new bug for the suspend problem? After suspend, bluetoothctl no longer discovers audio devices, although other computers are still discovered. A reboot restores the ability to discover audio devices. --- Additional comment from Stuart D Gathman on 2014-09-16 10:36:53 EDT --- I considered it "working" when it was only broken by suspend. However, it is totally broken again - even after reboot. That is why I asked about creating a new bug for the suspend problem. Even rebooting with working kernel (kernel-3.15.10-201.fc20.i686), the audio stream is still broken. So there is also a problem somewhere in the stack from pulseaudio to kernel after the updates. --- Additional comment from Rex Dieter on 2014-09-16 10:51:34 EDT --- It's usually best to track one issue per bug, so doing a new bug makes sense.
For a few *glorious* weeks, we had working bluetooth audio in F20 (other than not surviving suspend/resume - a relatively minor issue). Sadly, another round of updates, and it is broken again - even after reboot. Now, I still have a laptop that works, because it hasn't been updated. So I will try to do a meaningful diff between rpm -qa on the two laptops - maybe that will provide a clue. This is complicated by one being x86_64 and the other i686.
With kernel-3.16, bluetoothctl fails to connect at all, giving this oops in journalctl: Sep 21 15:19:49 elissa.gathman.org kernel: CPU: 0 PID: 2299 Comm: kworker/u5:1 Tainted: G W 3.16.2-201.fc20.i686 #1 Sep 21 15:19:49 elissa.gathman.org kernel: Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A16 10/16/2008 Sep 21 15:19:49 elissa.gathman.org kernel: Workqueue: hci0 hci_conn_timeout [bluetooth] Sep 21 15:19:49 elissa.gathman.org kernel: c0c8b907 0fa8c735 00000000 e37e1e84 c0a00dde 00000000 e37e1eb4 c04506de Sep 21 15:19:49 elissa.gathman.org kernel: c0bab950 00000000 000008fb fa06591d 00000128 fa02ff1d fa02ff1d e14b2c98 Sep 21 15:19:49 elissa.gathman.org kernel: ffffffff e14b2c00 e37e1ec4 c04507e2 00000009 00000000 e37e1f00 fa02ff1d Sep 21 15:19:49 elissa.gathman.org kernel: Call Trace: Sep 21 15:19:49 elissa.gathman.org kernel: [<c0a00dde>] dump_stack+0x41/0x52 Sep 21 15:19:49 elissa.gathman.org kernel: [<c04506de>] warn_slowpath_common+0x7e/0xa0 Sep 21 15:19:49 elissa.gathman.org kernel: [<fa02ff1d>] ? hci_conn_timeout+0x6d/0x280 [bluetooth] Sep 21 15:19:49 elissa.gathman.org kernel: [<fa02ff1d>] ? hci_conn_timeout+0x6d/0x280 [bluetooth] Sep 21 15:19:49 elissa.gathman.org kernel: [<c04507e2>] warn_slowpath_null+0x22/0x30 Sep 21 15:19:49 elissa.gathman.org kernel: [<fa02ff1d>] hci_conn_timeout+0x6d/0x280 [bluetooth] Sep 21 15:19:49 elissa.gathman.org kernel: [<c0468275>] process_one_work+0x115/0x380 Sep 21 15:19:49 elissa.gathman.org kernel: [<c0468a40>] worker_thread+0xf0/0x470 Sep 21 15:19:49 elissa.gathman.org kernel: [<c048ed1f>] ? __wake_up_locked+0x1f/0x30 Sep 21 15:19:49 elissa.gathman.org kernel: [<c0468950>] ? create_and_start_worker+0x50/0x50 Sep 21 15:19:49 elissa.gathman.org kernel: [<c046e1c6>] kthread+0xa6/0xc0 Sep 21 15:19:49 elissa.gathman.org kernel: [<c0a077c1>] ret_from_kernel_thread+0x21/0x30 Sep 21 15:19:49 elissa.gathman.org kernel: [<c046e120>] ? insert_kthread_work+0x30/0x30 Sep 21 15:19:49 elissa.gathman.org kernel: ---[ end trace 9534c2290f621a46 ]---
With kernel-3.15, bluetoothctl connects, but there is still no audio. The bluetooth audio does not show up in pulseaudio. Unlike the f19 version of this bug, there are no errors in journalctl to give a clue as to what is breaking. It just doesn't work. Comparing some modules with the still working (unupdated) laptop, maybe these are relevant: 402c454 < gstreamer1-libav-1.2.4-1.fc20 --- > gstreamer1-libav-1.2.4-2.fc20 408c460 < gstreamer-ffmpeg-0.10.13-12.fc20 --- > gstreamer-ffmpeg-0.10.13-13.fc20 411c463 < gstreamer-plugins-espeak-0.4.0-2.fc19.x86_64 --- > gstreamer-plugins-espeak-0.4.0-2.fc19.i686 413d464 < gstreamer-plugins-good-extras-0.10.31-10.fc20
Looks like you have several issues going on here, moving forward probably best to focus on the "kernel-3.16 bluetooth driver" crash part. Reassigning.
*** This bug has been marked as a duplicate of bug 1124996 ***
Oh sorry, I failed to read all the comments, and now we've come full circle (cloning bug #foo, then getting the cloned bug #foo dup'd against the original report). I'm not sure how best to handle cases like this, but I can say it's a little confusing tracking multiple issues per bug (and combining that with cloned bugs).
There are 3 separate issues. 1) the kernel breaks with 3.16 2) When the kernel was working, it would not work after suspend/resume 3) Even when the kernel is working, and the device can connect, there is still no bluetooth audio device in pulseaudio since some update after Sep 03.