Hello everyone,
I’m posting to report a significant regression issue I’ve encountered with the Bluetooth service on Fedora 42. Since upgrading to BlueZ versions 5.83 and 5.84, the automatic A2DP profile (high-quality audio) connection fails upon system startup.
The devices I’m testing with are my Xiaomi Redmi Buds 6 Lite and Redmi Buds 5.
The Connection Problem
The main symptom is that the earbuds appear to initiate a connection, but fail to complete it correctly and disconnect immediately.
The system then incorrectly defaults to the HSP profile (low-quality voice audio). This results in several errors in the system logs and an unstable audio experience, with intermittent sound loss, even after manually switching profiles.
The issue is a clear regression:
- Problematic Versions: BlueZ 5.83 and 5.84.
- Working Version: BlueZ 5.80 works perfectly, establishing the A2DP profile correctly and automatically. This is the only older version I was able to test due to repository availability.
- The issue affects all codecs (SBC, AAC, and SBC-XQ).
Temporary Workaround
I found that I can establish a successful, stable A2DP connection by performing a manual step:
- Restarting the
bluetooth.serviceafter boot, or - Manually connecting the earbuds again from the KDE Bluetooth settings once they appear as disconnected.
System Details
| Component | Detail |
|---|---|
| Distribution | Fedora 42 (KDE Spin) |
| Bluetooth Adapter | TP-Link UB500 Plus |
| Adapter Chipset | Realtek RTL8761BU |
| Problematic BlueZ | 5.84 (also verified with 5.83) |
Exportar a Hojas de cálculo
Relevant System Logs
Here are the key lines from journalctl showing the failure on startup (marked by the error updating services and Transport endpoint is not connected messages) and the subsequent attempt to stop/restart the service.
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)
Is anyone else experiencing similar A2DP connection issues with BlueZ versions 5.83/5.84? I’m curious if this regression affects other Bluetooth chipsets or devices as well. Any insight would be appreciated! 
BlueZ GitHub Issue:
Fedora Bugzilla Entry: