Bug 1257863
| Summary: | bluetooth headphones skips often | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomasz Torcz <tomek> |
| Component: | pulseaudio | Assignee: | Lennart Poettering <lpoetter> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 27 | CC: | aizuddin.zali, dominik, eocallaghan, jan.public, lkundrak, lpoetter, mike, npmccallum, rdieter, sbandyop, teppot, wtaymans, yannik |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | pulseaudio-12.0-3.fc28 pulseaudio-12.0-3.fc27 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-07-11 20:16:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Still happens with: kernel-core-4.3.0-0.rc2.git1.1.fc24.x86_64 pulseaudio-7.0-1.fc24.x86_64 bluez-5.34-1.fc24.x86_64 Sorry, can't help with that. I have the same issue also! It's not a range thing either because the speaker is right next to the laptop. $ rpm -q kernel-core pulseaudio bluez kernel-core-4.2.5-300.fc23.x86_64 pulseaudio-7.0-1.fc23.x86_64 bluez-5.35-1.fc23.x86_64 This is on a fresh copy of Fedora 23/KDE. @Tomasz, What controller do you have? Mine is the following: $ lsusb | grep Blue Bus 004 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Cheers, Edward. My controller is: Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) I do have the same problems with a USB bluetooth dongle: Bus 001 Device 017: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) but also with a 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) that has a integrated bluetooth controller. I tried changing /etc/pulse/daemon.conf to no avail. Additional information: This is a fresh Fedora 23 x64 installation on a Dell XPS 15. $ dnf list installed bluez* bluez.x86_64 5.36-1.fc23 @updates bluez-cups.x86_64 5.36-1.fc23 @updates bluez-libs.x86_64 5.36-1.fc23 @updates $ dnf list installed pulse* pulseaudio.x86_64 7.1-1.fc23 @updates pulseaudio-gdm-hooks.x86_64 7.1-1.fc23 @updates pulseaudio-libs.i686 7.1-1.fc23 @updates pulseaudio-libs.x86_64 7.1-1.fc23 @updates pulseaudio-libs-glib2.x86_64 7.1-1.fc23 @updates pulseaudio-module-bluetooth.x86_64 7.1-1.fc23 @updates pulseaudio-module-x11.x86_64 7.1-1.fc23 @updates pulseaudio-utils.x86_64 7.1-1.fc23 @updates Bluetooth audio works fine in Ubuntu 15.10 x64 with the following versions: bluez 5.35-0ubuntu2 bluez-cups 5.35-0ubuntu2 bluez-obexd 5.35-0ubuntu2 gstreamer0.10-pulseaudio:amd64 0.10.31-3+nmu4ubuntu2~gcc5.1 gstreamer1.0-pulseaudio:amd64 1.6.0-1ubuntu1 pulseaudio pulseaudio-module-bluetooth 1:6.0-0ubuntu13 pulseaudio-module-x11 1:6.0-0ubuntu13 pulseaudio-utils 1:6.0-0ubuntu13 On Fedora 23 I do experience the same stuttering with these journalctl entries: sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 82927 us (= 14628 bytes) in audio stream This makes bluetooth audio completely unasble. It also happens when being within 50 centimeters of the bluetooth receiver, a Philips AEA2700: Name: Philips AEA2700 Alias: Philips AEA2700 Class: 0x240414 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase It doesn't really matter what it's reported against, it affects _all_ linuxes that involve modern pulseaudio and bluez unfortunately. This is not a RH/Fedora specific bug and should be dealt with upstream: https://bugs.freedesktop.org/show_bug.cgi?id=58746 Fantastically and in true linux fashion, I myself have tried every possible combination of bluetooth headphone and dongle, those with proprietary blobs for drivers, those with completely open drivers, a slew of headphones... They all work perfectly on Windows and Android... Skipping has the effect of rate-limiting the playback buffer and the audio syncs when you re-enter the signal area. Literally the only OS that isn't handling this properly at the moment is desktop Linux. This bug makes it impossible to watch movies with a Bluetooth headset. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. While searching what I understand is it is a very common issue. What I do not understand is why it is not being fixed, the upstream bug was reported on 2012-12-25 and from the progress it does not look like going to be fixed any time soon. From a user's perspective, starting from pairing devices to connecting to a device, everything looks so unstable and buggy in Fedora 27 workstation and I have to check logs /search BZs / troubleshoot things instead of being able to listen to music peacefully !!!! And no its *not* buggy devices as it works well in android/mac so may be we should fix the implementation! ~~~ Dec 26 13:48:35 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 8810 us (= 1552 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5795 us (= 1020 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5799 us (= 1020 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 4809 us (= 848 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 4766 us (= 840 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 2123 us (= 372 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5807 us (= 1024 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 29783 us (= 5252 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 31803 us (= 5608 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5760 us (= 1016 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 30801 us (= 5432 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 31799 us (= 5608 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 3764 us (= 660 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 1153 us (= 200 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5773 us (= 1016 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5805 us (= 1024 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 29791 us (= 5252 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 5804 us (= 1020 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 30783 us (= 5428 bytes) in audio stream Dec 26 13:48:36 hostname.example.com pulseaudio[3630]: [bluetooth] module-bluez5-device.c: Skipping 31792 us (= 5608 bytes) in audio stream ~~~ It looks like this was fixed upstream in https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=192c3aaef8352ba9504aee4e311a23f6162d39d8 and is included in pulseaudio 12.0 release. Could someone backport this to F27+? pulseaudio-12.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0ca2efd3f6 pulseaudio-12.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-55824401dc pulseaudio-12.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-55824401dc pulseaudio-12.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0ca2efd3f6 pulseaudio-12.0-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0ca2efd3f6 pulseaudio-12.0-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-55824401dc pulseaudio-12.0-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-55824401dc This still persists for me (even though maybe to a bit lesser degree than before - I'm not entirely sure) I am using pulseaudio 12.0-1.fc28 from testing. pulseaudio-12.0-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0ca2efd3f6 pulseaudio-12.0-3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0ca2efd3f6 pulseaudio-12.0-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-55824401dc pulseaudio-12.0-3.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-55824401dc pulseaudio-12.0-3.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0ca2efd3f6 pulseaudio-12.0-3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. pulseaudio-12.0-3.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: While playing music, every few 5-7 seconds there's a pause for about 1 second. Headphones are connected by bluetooth, use A2DP profile. [HS-BT01]# info Device 74:FD:A0:01:46:5D Name: HS-BT01 Alias: HS-BT01 Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb There are following entries in logs during the incidents: sie 28 10:58:51 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 46069 us (= 8124 bytes) in audio stream sie 28 10:58:51 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 31084 us (= 5480 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 32250 us (= 5688 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 82927 us (= 14628 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 47068 us (= 8300 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 31079 us (= 5480 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 37088 us (= 6540 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 82091 us (= 14480 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 45067 us (= 7948 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 32094 us (= 5660 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 34067 us (= 6008 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 83097 us (= 14656 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 54069 us (= 9536 bytes) in audio stream sie 28 10:58:52 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 31080 us (= 5480 bytes) in audio stream sie 28 10:58:53 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 33091 us (= 5836 bytes) in audio stream sie 28 10:58:53 microstation pulseaudio[2869]: [bluetooth] module-bluez5-device.c: Skipping 83093 us (= 14656 bytes) in audio stream Version-Release number of selected component (if applicable): pulseaudio-6.0-8.fc23.x86_64 bluez-5.33-1.fc24.x86_64 kernel-core-4.2.0-0.rc8.git0.1.fc24.x86_64 How reproducible: Very often. Going to bluetooth control panel, disconnecting headphones and reconnecting them fixes it sometimes. But even after reconnect, the problem reappears after 1-2 hours of playback.