Fedora Linux 42, stable (no testing repos) bluez version: 5.83-1.fc42 Bluetooth stack: bluez + PipeWire Headset: Anker Soundcore Q30 (Noise-Cancelling Bluetooth headphone) 1. Perform `sudo dnf update` → bluez-5.83-1.fc42 installed. 2. Reboot or log out/in. 3. Enable Bluetooth and put Soundcore Q30 into pairing mode. 4. Connect the headset via KDE settings. 5. Observe a stable connection for ~5 seconds. 6. Headset disconnects automatically (A2DP profile disappears). 7. Restart Bluetooth service (`sudo systemctl restart bluetooth`) → reconnects and works. Expected: Headset stays connected with A2DP until manual disconnect. Actual: Disconnects automatically after ~5 seconds; only fixed by restarting bluetooth.service. Problem appeared only after upgrading to bluez-5.83-1.fc42; no issues on bluez-5.81-2.fc42. - Restarting bluetooth.service restores functionality temporarily. - Downgrading to bluez-5.81-2.fc42 restores stable connections permanently. Note: The issue has been occurring continuously for the past 5 days since the update. Reproducible: Always Steps to Reproduce: 1.sudo dnf update → bluez 5.83-1.fc42 installed. 2.Reboot or log out/in. 3.Enable Bluetooth and put Q30 in pairing mode. 4.Connect via KDE. 5.Observe brief stable connection (~5 seconds), then disconnection. 6.Run sudo systemctl restart bluetooth. 7.Reconnect – stable connection restored. Actual Results: A2DP profile drops after ~5 seconds post-pairing; no audio output. Bluetooth service must be restarted as workaround. Expected Results: Soundcore Q30 should remain connected with A2DP profile until manually disconnected. Additional Information: - Regression appears in 5.83-1.fc42; no issues on 5.81. - Device is a widely-used NC headphone in daily professional use. - Restart workaround is disruptive in workflow.
This issue has also been reported upstream in the BlueZ project: “Soundcore Q30 disconnects after a few seconds ...” – see GitHub issue #1330. https://github.com/bluez/bluez/issues/1330
FEDORA-2025-c10d623d39 (bluez-5.83-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c10d623d39
FEDORA-2025-e53a11a6d0 (bluez-5.83-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-e53a11a6d0
FEDORA-2025-c10d623d39 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c10d623d39` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c10d623d39 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-e53a11a6d0 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e53a11a6d0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e53a11a6d0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c10d623d39 (bluez-5.83-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
Created attachment 2097070 [details] btmon & journal logs – cold boot (failure) vs. “systemctl restart bluetooth” (works) The ZIP archive contains four files to illustrate the difference between “cold boot → audio stream drops after ~5 s” and “bluetooth service restart → stream remains stable”: btmon_boot.snoop btmon trace after a fresh system boot journal_boot.txt journalctl -b from the same session btmon_after_restart.snoop btmon trace after sudo systemctl restart bluetooth journal_after_restart.txt journalctl immediately after restarting the service Reproduction steps: Boot the system normally (bluetooth.service starts automatically). Pair the Soundcore Q30 and start an audio stream → it drops after ~5 s. ► Logs: btmon_boot.snoop + journal_boot.txt sudo systemctl restart bluetooth Reconnect the headset → the stream remains stable. ► Logs: btmon_after_restart.snoop + journal_after_restart.txt Observation: In the failure case, the HCI log shows an “Authentication Failure (0x05)” immediately before the disconnect; this does not occur after the service restart. System information: Fedora 42 Kernel: 6.15.5-200.fc42.x86_64 bluez: 5.83-2.fc42 (behavior is identical to 5.83-1.fc42) Issue is reproducible with Soundcore Liberty Neo as well The .snoop files can be opened in Wireshark using the “Bluetooth HCI snoop log” file type.
The issue in bluez-5.83-1.fc42 remains unresolved and was closed prematurely. I have uploaded additional HCI and journal logs that clearly demonstrate the fault—on cold boot the audio stream drops after ~5 s, and only stabilizes after systemctl restart bluetooth. Please reopen this bug for further investigation.
FEDORA-2025-e53a11a6d0 (bluez-5.83-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
I am experiencing the same problem on Fedora 42 KDE. Affected versions: Kernel: 6.16.4-200.fc42.x86_64 BlueZ: bluez.x86_64 5.80-1.fc42 The only solution I found was to downgrade BlueZ to 6.16.4-200.fc42.x86_64.
Sorry, the affected version of BlueZ is bluez.x86_64 5.83-2.fc42