On Fedora 42, BlueZ versions 5.83 and 5.84 fail to connect my Xiaomi Redmi Buds 6 Lite and Redmi Buds 5 to the A2DP profile on system startup. The connection attempts default to the HSP profile instead, leading to errors and connection instability. The problem affects A2DP functionality regardless of the codec used (SBC, AAC, or SBC-XQ). Additional Information: Working BlueZ Version: 5.80 (the only older version available for testing in the Fedora repositories). Problematic BlueZ Version: 5.84 (also verified with 5.83) Bluetooth Adapter: TP-Link UB500 Plus (Chipset: Realtek RTL8761BU) Bluetooth Devices: Xiaomi Redmi Buds 6 Lite and Redmi Buds 5 Affected Codecs: SBC, AAC, SBC-XQ The problem is a regression: This issue was not present in BlueZ 5.80. The downgrade to this version resolves the problem, indicating a significant change in the software's behavior in later versions. Reproducible: Always Steps to Reproduce: 1. Have a PC running Fedora with a BlueZ version of 5.83 or newer. 2. Pair either the **Redmi Buds 6 Lite** or **Redmi Buds 5**. 3. Shut down the PC and ensure the earbuds are turned on. 4. Boot the PC. The earbuds will fail to connect automatically to the A2DP profile. Actual Results: The earbuds do not connect automatically. The journalctl logs show the following errors: sep 24 16:28:45 Ryzen-PC bluetoothd[1188]: Failed to set mode: Not Supported (0x0c) sep 24 16:29:05 Ryzen-PC bluetoothd[1188]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sep 24 16:31:09 Ryzen-PC bluetoothd[1188]: No matching connection for device sep 24 16:31:24 Ryzen-PC bluetoothd[1188]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sep 24 16:31:24 Ryzen-PC bluetoothd[1188]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) sep 24 16:56:04 Ryzen-PC systemd[1]: Stopping bluetooth.service - Bluetooth service... sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Terminating sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: src/bearer.c:btd_bearer_disconnected() Unknown disconnection value: 21 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: src/device.c:device_disconnected() Unknown disconnection value: 21 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) sep 24 16:56:39 Ryzen-PC bluetoothd[1193]: Failed to set mode: Not Supported (0x0c) sep 24 16:56:58 Ryzen-PC bluetoothd[1193]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) After manual intervention (reconnecting via settings or restarting the Bluetooth service), a connection can be established, but the audio is sometimes unstable, particularly on one side, before it finally stabilizes. Expected Results: The Redmi Buds should automatically connect to the A2DP profile with the selected codec upon system startup, with stable audio output, as it does with BlueZ 5.80. Additional Information: Relevant journalctl output: sep 24 16:28:45 Ryzen-PC systemd[1]: Started bluetooth.service - Bluetooth service. sep 24 16:28:45 Ryzen-PC bluetoothd[1188]: Starting SDP server sep 24 16:28:45 Ryzen-PC bluetoothd[1188]: Bluetooth management interface 1.23 initialized sep 24 16:28:45 Ryzen-PC bluetoothd[1188]: Battery Provider Manager created sep 24 16:28:45 Ryzen-PC bluetoothd[1188]: Failed to set mode: Not Supported (0x0c) sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1 sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0 sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05 sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05 sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex sep 24 16:28:53 Ryzen-PC bluetoothd[1188]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex sep 24 16:29:05 Ryzen-PC bluetoothd[1188]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sep 24 16:31:09 Ryzen-PC bluetoothd[1188]: No matching connection for device sep 24 16:31:24 Ryzen-PC bluetoothd[1188]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sep 24 16:31:24 Ryzen-PC bluetoothd[1188]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) sep 24 16:56:04 Ryzen-PC systemd[1]: Stopping bluetooth.service - Bluetooth service... sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Terminating sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: src/bearer.c:btd_bearer_disconnected() Unknown disconnection value: 21 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: src/device.c:device_disconnected() Unknown disconnection value: 21 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05 sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Endpoint unregistered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Battery Provider Manager destroyed sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Stopping SDP server sep 24 16:56:04 Ryzen-PC bluetoothd[1188]: Exit sep 24 16:56:04 Ryzen-PC systemd[1]: bluetooth.service: Deactivated successfully. sep 24 16:56:04 Ryzen-PC systemd[1]: Stopped bluetooth.service - Bluetooth service. -- Boot 5af7d34ff2e94452aba4d99c4bb55cff -- sep 24 16:56:39 Ryzen-PC systemd[1]: Starting bluetooth.service - Bluetooth service... sep 24 16:56:39 Ryzen-PC bluetoothd[1193]: Bluetooth daemon 5.84 sep 24 16:56:39 Ryzen-PC bluetoothd[1193]: Starting SDP server sep 24 16:56:39 Ryzen-PC systemd[1]: Started bluetooth.service - Bluetooth service. sep 24 16:56:39 Ryzen-PC bluetoothd[1193]: Bluetooth management interface 1.23 initialized sep 24 16:56:39 Ryzen-PC bluetoothd[1193]: Battery Provider Manager created sep 24 16:56:39 Ryzen-PC bluetoothd[1193]: Failed to set mode: Not Supported (0x0c) sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/ldac sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/aptx_hd sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_hd sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/aptx sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/aac sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aac sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/opus_g sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/opus_g sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/sbc sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/sbc sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_1 sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_0 sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/faststream sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/faststream_duplex sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/opus_05 sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/opus_05 sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/opus_05_duplex sep 24 16:56:47 Ryzen-PC bluetoothd[1193]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/opus_05_duplex sep 24 16:56:58 Ryzen-PC bluetoothd[1193]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) BlueZ GitHub Issue: https://github.com/bluez/bluez/issues/1570 Fedora Discussion Thread: https://discussion.fedoraproject.org/t/bluetooth-a2dp-regression-in-bluez-5-83-5-84-connection-fails-on-startup-tp-link-ub500-plus/165055
This looks the same as bug 2397631 but they report it works with 5.83 and is just a regression in 5.84. I suspect 5.83 is fine else there would have been a report some time ago, please confirm.
I can confirm this is not limited to 5.84 on my system. I had bluez-5.83-2 installed and it did not work correctly. I then downgraded to bluez-5.80-1.fc42.x86_64, which worked fine. I also just tested bluez-5.84-1 — it still does not work correctly. So on my hardware/installation the problem is present in 5.83-2 and 5.84-1; 5.80 appears to be working.
FEDORA-2025-1c4ded4bf6 (bluez-5.84-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c4ded4bf6
FEDORA-2025-6305936bf0 (bluez-5.84-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6305936bf0
FEDORA-2025-d7bf6d2fbe (bluez-5.84-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d7bf6d2fbe
I just installed bluez-5.84-2.fc42 (https://bodhi.fedoraproject.org/updates/FEDORA-2025-6305936bf0 ) and I'm still having the same issues. I'm attaching the logs, and I'm available to provide any other information that might help. Logs: Bluez 5.84-2 just installed: journalctl -u bluetooth.service sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Bluetooth daemon 5.84 sep 25 18:01:01 Ryzen-PC systemd[1]: Started bluetooth.service - Bluetooth service. sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Starting SDP server sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Bluetooth management interface 1.23 initialized sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Battery Provider Manager created sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/ldac sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/aptx_hd sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_hd sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/aptx sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/aac sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aac sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/opus_g sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/opus_g sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/sbc sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/sbc sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_1 sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_0 sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/faststream sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/faststream_duplex sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/opus_05 sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/opus_05 sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSink/opus_05_duplex sep 25 18:01:01 Ryzen-PC bluetoothd[20324]: Endpoint registered: sender=:1.51 path=/MediaEndpoint/A2DPSource/opus_05_duplex sep 25 18:02:25 Ryzen-PC bluetoothd[20324]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107) sep 25 18:02:45 Ryzen-PC bluetoothd[20324]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sudo journalctl -k -b -1 | grep -i blue sep 25 18:01:59 Ryzen-PC kernel: Bluetooth: Dropping L2CAP data: receive buffer overflow ~ After reboot: journalctl -u bluetooth.service sep 25 18:05:12 Ryzen-PC systemd[1]: Starting bluetooth.service - Bluetooth service... sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Bluetooth daemon 5.84 sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Starting SDP server sep 25 18:05:12 Ryzen-PC systemd[1]: Started bluetooth.service - Bluetooth service. sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Bluetooth management interface 1.23 initialized sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Battery Provider Manager created sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex sep 25 18:05:33 Ryzen-PC bluetoothd[1184]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sudo journalctl -k --no-pager | grep -i blue sep 25 18:05:02 Ryzen-PC kernel: usb 3-4.4: Product: TP-Link Bluetooth USB Adapter sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: Core ver 2.22 sep 25 18:05:11 Ryzen-PC kernel: NET: Registered PF_BLUETOOTH protocol family sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: HCI device and connection manager initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: HCI socket layer initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: L2CAP socket layer initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: SCO socket layer initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922 sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: BNEP filters: protocol multicast sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: BNEP socket layer initialized sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: MGMT ver 1.23 sep 25 18:05:20 Ryzen-PC kernel: Bluetooth: RFCOMM TTY layer initialized sep 25 18:05:20 Ryzen-PC kernel: Bluetooth: RFCOMM socket layer initialized sep 25 18:05:20 Ryzen-PC kernel: Bluetooth: RFCOMM ver 1.11 sep 25 18:05:23 Ryzen-PC kernel: Bluetooth: Dropping L2CAP data: receive buffer overflow sep 25 18:06:29 Ryzen-PC kernel: Bluetooth: Dropping L2CAP data: receive buffer overflow sep 25 18:10:35 Ryzen-PC kernel: Bluetooth: hci0: SCO packet for unknown connection handle 3 sep 25 18:10:35 Ryzen-PC kernel: Bluetooth: hci0: SCO packet for unknown connection handle 3 sudo dmesg | grep -i blue [ 4.268946] usb 3-4.4: Product: TP-Link Bluetooth USB Adapter [ 13.762913] Bluetooth: Core ver 2.22 [ 13.763109] NET: Registered PF_BLUETOOTH protocol family [ 13.763112] Bluetooth: HCI device and connection manager initialized [ 13.763118] Bluetooth: HCI socket layer initialized [ 13.763123] Bluetooth: L2CAP socket layer initialized [ 13.763133] Bluetooth: SCO socket layer initialized [ 13.909459] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 13.910473] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 13.910478] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 13.925225] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 13.928054] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 14.077454] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 15.400932] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.400939] Bluetooth: BNEP filters: protocol multicast [ 15.400945] Bluetooth: BNEP socket layer initialized [ 15.402576] Bluetooth: MGMT ver 1.23 [ 22.973358] Bluetooth: RFCOMM TTY layer initialized [ 22.973372] Bluetooth: RFCOMM socket layer initialized [ 22.973380] Bluetooth: RFCOMM ver 1.11 [ 25.689309] Bluetooth: Dropping L2CAP data: receive buffer overflow [ 91.211431] Bluetooth: Dropping L2CAP data: receive buffer overflow [ 337.384668] Bluetooth: hci0: SCO packet for unknown connection handle 3 [ 337.384675] Bluetooth: hci0: SCO packet for unknown connection handle 3 sudo journalctl -b | grep -i bluez sep 25 18:05:14 Ryzen-PC NetworkManager[1366]: <info> [1758834314.5884] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.52.1-1.fc42/libnm-device-plugin-bluetooth.so) sep 25 18:05:33 Ryzen-PC kded6[2084]: kf.bluezqt: PendingCall Error: "br-connection-create-socket" sep 25 18:06:29 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+NREC=0 sep 25 18:06:29 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,110,100,99,255,1 sep 25 18:06:29 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+XIAOMI=FF01020101150004017BFF050B200501011B070001000205020C00FF sep 25 18:06:39 Ryzen-PC kded6[2084]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:06:39 Ryzen-PC plasmashell[2121]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:06:39 Ryzen-PC systemsettings[3441]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:08:25 Ryzen-PC bluetoothd[1184]: /org/bluez/hci0/dev_68_4D_B6_08_80_E3/sep1/fd1: fd(42) ready sep 25 18:09:06 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: FF sep 25 18:09:38 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: FF sep 25 18:10:13 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: FF sep 25 18:10:25 Ryzen-PC kded6[2084]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:25 Ryzen-PC plasmashell[2121]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:26 Ryzen-PC systemsettings[3934]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:26 Ryzen-PC systemsettings[3934]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:35 Ryzen-PC kded6[2084]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:35 Ryzen-PC plasmashell[2121]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:35 Ryzen-PC systemsettings[3934]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:35 Ryzen-PC systemsettings[3934]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:43 Ryzen-PC kded6[2084]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:43 Ryzen-PC plasmashell[2121]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:43 Ryzen-PC systemsettings[3934]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:43 Ryzen-PC plasmashell[2121]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:10:43 Ryzen-PC systemsettings[3934]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:12:17 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: FF sep 25 18:12:25 Ryzen-PC kded6[2084]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:12:25 Ryzen-PC plasmashell[2121]: org.kde.pulseaudio: No object for name "bluez_output.68_4D_B6_08_80_E3.1" sep 25 18:12:26 Ryzen-PC bluetoothd[1184]: /org/bluez/hci0/dev_68_4D_B6_08_80_E3/sep2/fd2: fd(42) ready sep 25 18:15:26 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: FF sep 25 18:19:37 Ryzen-PC wireplumber[1839]: spa.bluez5.native: RFCOMM receive command but modem not available: FF sudo journalctl -b | grep -i bluetooth sep 25 18:05:02 Ryzen-PC kernel: usb 3-4.4: Product: TP-Link Bluetooth USB Adapter sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: Core ver 2.22 sep 25 18:05:11 Ryzen-PC kernel: NET: Registered PF_BLUETOOTH protocol family sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: HCI device and connection manager initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: HCI socket layer initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: L2CAP socket layer initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: SCO socket layer initialized sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 sep 25 18:05:11 Ryzen-PC kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922 sep 25 18:05:12 Ryzen-PC systemd[1]: Starting bluetooth.service - Bluetooth service... sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Bluetooth daemon 5.84 sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Starting SDP server sep 25 18:05:12 Ryzen-PC systemd[1]: Started bluetooth.service - Bluetooth service. sep 25 18:05:12 Ryzen-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' sep 25 18:05:12 Ryzen-PC systemd[1]: Reached target bluetooth.target - Bluetooth Support. sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: BNEP filters: protocol multicast sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: BNEP socket layer initialized sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Bluetooth management interface 1.23 initialized sep 25 18:05:12 Ryzen-PC kernel: Bluetooth: MGMT ver 1.23 sep 25 18:05:12 Ryzen-PC bluetoothd[1184]: Battery Provider Manager created sep 25 18:05:14 Ryzen-PC NetworkManager[1366]: <info> [1758834314.5884] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.52.1-1.fc42/libnm-device-plugin-bluetooth.so) sep 25 18:05:20 Ryzen-PC kernel: Bluetooth: RFCOMM TTY layer initialized sep 25 18:05:20 Ryzen-PC kernel: Bluetooth: RFCOMM socket layer initialized sep 25 18:05:20 Ryzen-PC kernel: Bluetooth: RFCOMM ver 1.11 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/ldac sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx_hd sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_hd sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aptx sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/aac sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aac sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_g sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_g sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/sbc sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/sbc sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_1 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_0 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/faststream_duplex sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05 sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink/opus_05_duplex sep 25 18:05:20 Ryzen-PC bluetoothd[1184]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource/opus_05_duplex sep 25 18:05:22 Ryzen-PC systemd[1565]: Starting obex.service - Bluetooth OBEX service... sep 25 18:05:22 Ryzen-PC systemd[1565]: Started obex.service - Bluetooth OBEX service. sep 25 18:05:23 Ryzen-PC systemd[1565]: Reached target bluetooth.target - Bluetooth. sep 25 18:05:23 Ryzen-PC kernel: Bluetooth: Dropping L2CAP data: receive buffer overflow sep 25 18:05:33 Ryzen-PC bluetoothd[1184]: src/device.c:search_cb() 68:4D:B6:08:80:E3: error updating services: Input/output error (5) sep 25 18:06:29 Ryzen-PC kernel: Bluetooth: Dropping L2CAP data: receive buffer overflow sep 25 18:08:25 Ryzen-PC bluetoothd[1184]: /org/bluez/hci0/dev_68_4D_B6_08_80_E3/sep1/fd1: fd(42) ready sep 25 18:10:35 Ryzen-PC kernel: Bluetooth: hci0: SCO packet for unknown connection handle 3 sep 25 18:10:35 Ryzen-PC kernel: Bluetooth: hci0: SCO packet for unknown connection handle 3 sep 25 18:12:26 Ryzen-PC bluetoothd[1184]: /org/bluez/hci0/dev_68_4D_B6_08_80_E3/sep2/fd2: fd(42) ready
FEDORA-2025-1c4ded4bf6 has been pushed to the Fedora 43 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-1c4ded4bf6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c4ded4bf6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I’ve already tested version bluez-5.84-2.fc42.x86_64 (I downloaded it from https://koji.fedoraproject.org/koji/buildinfo?buildID=2830612 ), but I’m still having the same issue. In my previous message, I attached different logs from my system that might help determine what the problem is. I’m available to provide any other information that could be useful. It’s worth noting that version 5.80 works correctly for me. rpm -qa | grep -i bluez bluez-5.84-2.fc42.x86_64 bluez-libs-5.84-2.fc42.x86_64 bluez-obexd-5.84-2.fc42.x86_64 bluez-cups-5.84-2.fc42.x86_64 bluez-libs-5.84-2.fc42.i686 bluez-tools-0.2.0-0.27.git20170912.7cb788c.fc42.x86_64 kf6-bluez-qt-6.18.0-1.fc42.x86_64 uname -r 6.16.8-200.fc42.x86_64
FEDORA-2025-6305936bf0 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-6305936bf0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6305936bf0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d7bf6d2fbe 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-d7bf6d2fbe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d7bf6d2fbe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-6305936bf0 (bluez-5.84-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
I think this discussion forum thread is related to my error: https://discussion.fedoraproject.org/t/bluetooth-service-needs-to-be-restarted-to-work/156298
FEDORA-2025-1c4ded4bf6 (bluez-5.84-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
> It’s worth noting that version 5.80 works correctly for me. Please test the intervening builds to determine what the last working/first failed builds were, they can be retrieved from koji. To date you're the only person who's reported issues (and audio issues are reported basically the moment they regress) so there's something quite specific in your setup. https://koji.fedoraproject.org/koji/packageinfo?packageID=6777
Hello, thanks for the response! Version 5.80-1.fc42 works fine Version 5.81-2.fc42 works fine Version 5.83-1.fc42 errors start when connecting the device at system startup Version 5.83-2.fc42 same problem Version 5.84-1.fc42 same problem Version 5.84-2.fc42 same problem Regarding the audio quality issues, I’m testing whether it has to do with having been using the SBC-XQ codec, which the headphones might not fully support. I’m trying AAC, and so far I haven’t had any problems.
> Regarding the audio quality issues, I’m testing whether it has to do with > having been using the SBC-XQ codec, which the headphones might not fully > support. I’m trying AAC, and so far I haven’t had any problems. That would be a different bug report with pipewire, as bluez doesn't deal directly with the audio streams, but reading up SBC-XQ looks to be somewhat of a hack [1] anyway so you may be better off with AAC. [1] https://soundexpert.org/articles/-/blogs/audio-quality-of-sbc-xq-bluetooth-audio-codec
(In reply to falacu from comment #13) > I think this discussion forum thread is related to my error: > https://discussion.fedoraproject.org/t/bluetooth-service-needs-to-be- > restarted-to-work/156298 And reading through that thread shows it seems to only be happening on KDE and not other desktop environments, which likely explains why I've not seen it reported until now, now the question is what KDE does differently to the A2DP that GNOME and other desktops don't that makes bluez misbehave.
So yesterday digging through a few posts on the forum from June when 5.83 landed there's at least a few that mention issues when used with KDE: https://discussion.fedoraproject.org/t/bluetooth-service-needs-to-be-restarted-to-work/156298 https://discussion.fedoraproject.org/t/bluetooth-is-extremely-bugged-out-in-f42-kde-also-in-f41-kde/158644 So it looks like some change in bluez that affects KDE in particular but isn't necessarily seen by gnome or other desktop users.
Thank you for your research, I think this is progress. I’m going to share it as well in the BlueZ report on GitHub.
Bluetooth device management is handled by Bluedevil through BluezQt, but Bluetooth audio in KDE Plasma is handled by PipeWire, so it should be the same across desktops.
FYI, I get a similar issue with my bluetooth mouse. To be honest, it's been happening for a month or two where, upon starting my computer, the mouse just won't connect. I have to go to system settings (With my keyboard only -- that was a challenge at first) to the bluetooth settings and cycle the bluetooth on/off switch. Then, the mouse works fine.
Here is a similar issue reported in CachyOS: https://discuss.cachyos.org/t/issue-with-bluetooth-headphone-disconnecting/14952
(In reply to Steve Cossette from comment #22) > FYI, I get a similar issue with my bluetooth mouse. KDE too? What sort of mouse?
(In reply to Neal Gompa from comment #21) > Bluetooth device management is handled by Bluedevil through BluezQt, but > Bluetooth audio in KDE Plasma is handled by PipeWire, so it should be the > same across desktops. I suspect it's more around the signaling/device management for the connection that pipewire directly. I wonder what bluedevil does differently that other desktops.
(In reply to Peter Robinson from comment #24) > (In reply to Steve Cossette from comment #22) > > FYI, I get a similar issue with my bluetooth mouse. > > KDE too? What sort of mouse? yeah KDE too. I have a Logitech MX Master 3 mouse. I'll try to post some logs, but last I checked there wasn't anything very telling tbh.
> yeah KDE too. I have a Logitech MX Master 3 mouse. That is what I guessed, that mouse is somewhat special when it comes to bluetooth. It's got history. I wonder if it's also LE related as I think most of the devices listed here at least support LE modes.
That explains why the only device I have this issue with is my brand new Sony WH-1000XM6 headphones (which is my only BLE device). I don't observe this with my controllers or my Raycon Impact Earbuds.
(In reply to Peter Robinson from comment #27) > > yeah KDE too. I have a Logitech MX Master 3 mouse. > > That is what I guessed, that mouse is somewhat special when it comes to > bluetooth. It's got history. > > I wonder if it's also LE related as I think most of the devices listed here > at least support LE modes. Well, if it becomes enough of a PITA I might just revert to using the Logitech Unifying dongle then I guess. I don't really wanna waste a port for it though
(In reply to Peter Robinson from comment #27) > > yeah KDE too. I have a Logitech MX Master 3 mouse. > > That is what I guessed, that mouse is somewhat special when it comes to > bluetooth. It's got history. > > I wonder if it's also LE related as I think most of the devices listed here > at least support LE modes. I tried the option ControllerMode = bredr in /etc/bluetooth/main.conf and the problem persists. # Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = bredr
I tried with the Sony WH-CH510 and with this device no issues arise when starting up the computer.
FEDORA-2025-d7bf6d2fbe (bluez-5.84-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
In the report on BlueZ’s GitHub (https://github.com/bluez/bluez/issues/1570#issuecomment-3381770473 ), I received the following reply: "You might want to test with: bluez/bluetooth-next@014b713 (https://github.com/bluez/bluetooth-next/commit/014b7133fa7b534d9149ae5126bbb9f4434e4ebb )" I’m not exactly sure how to test this at the moment. I might wait until it’s included in a new BlueZ release, but I wanted to share it here for reference.
> I’m not exactly sure how to test this at the moment. I might wait until it’s > included in a new BlueZ release, but I wanted to share it here for reference. That's a kernel patch so you might be waiting a while ;-) I can put the patch in my copr kernel for people to test. It will be a 6.17.x kernel.
Scratch kernel here with the patch is here, usual caveats that it won't work with secure boot etc applies: https://koji.fedoraproject.org/koji/taskinfo?taskID=137939503 If people can confirm this fixes the issue I can organise to get it added to the 6.17 builds.
I tested the kernel from the URL you shared, but unfortunately, the issue persists.
I just installed 6.17.4-200.fc42.x86_64, and the problem persists; however, with bluez 5.81-2, it works perfectly.
Yup, there's been no change so that would be expected. Someone who knows the KDE bluetooth stack is going to need to debug to work out what has changed in bluez that breaks that and not other desktops or what special stuff that KDE does.
(In reply to Peter Robinson from comment #38) > Yup, there's been no change so that would be expected. Someone who knows the > KDE bluetooth stack is going to need to debug to work out what has changed > in bluez that breaks that and not other desktops or what special stuff that > KDE does. I sent a ping to Nicolas Fella in Matrix to see if we can get some insight here.
Thanks! I also opened a report on KDE in case it helps: https://bugs.kde.org/show_bug.cgi?id=510916