Bug 510916

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***
SUMMARY

Paired Bluetooth headsets do not automatically connect to the **A2DP** profile on system startup when running **BlueZ 5.83** or **5.84**. Manual reconnection via KDE Bluetooth settings or restarting `bluetooth.service` restores A2DP functionality. **BlueZ 5.81-2** works as expected. All affected systems use **KDE Plasma** as the desktop environment.

STEPS TO REPRODUCE

1. Use a system running KDE Plasma with BlueZ **5.83** or **5.84** (e.g., Fedora Linux 42).
2. Pair an A2DP-capable Bluetooth headset (for example: Xiaomi Redmi Buds 6 Lite or Redmi Buds 5).
3. Shut down or reboot the system while the headset is powered on and nearby.
4. After startup, observe whether the headset connects automatically to A2DP.

OBSERVED RESULT

The headset appears connected but does **not** automatically use the A2DP profile. Audio output may be unavailable until manual reconnection through KDE Bluetooth settings or by restarting `bluetooth.service`, which restores proper A2DP audio.

EXPECTED RESULT

Paired A2DP headsets should automatically reconnect to the A2DP profile and provide stereo audio on system startup, as they do with **BlueZ 5.81-2**.

SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
BlueZ versions tested: **5.81-2** (working), **5.83**, **5.84** (regression)
Kernel Version: 6.17.4-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

Hardware / system details:

* Bluetooth adapter: TP-Link UB500 Plus (Realtek RTL8761BU)
* Headsets affected: Xiaomi Redmi Buds 6 Lite, Redmi Buds 5
* Headset not affected: **Sony WH-CH510** (connects normally)
* CPU: AMD Ryzen 5 2600 (6 cores, 12 threads)
* Memory: 16 GiB RAM (15.5 GiB usable)
* GPU: AMD Radeon RX 5500 XT
* Motherboard: Gigabyte B450M GAMING

RELATED REPORTS

This issue has been independently reported in several other trackers, all describing the same A2DP regression in KDE Plasma environments:

* Fedora Bugzilla — Bug 2397966: *Bluetooth A2DP connection fails on startup with BlueZ 5.83+ (KDE Plasma)*
  [https://bugzilla.redhat.com/show_bug.cgi?id=2397966](https://bugzilla.redhat.com/show_bug.cgi?id=2397966)
* Fedora Discussion — *Bluetooth A2DP Regression in BlueZ 5.83/5.84: Connection Fails on Startup (TP-Link UB500 Plus)*
  [https://discussion.fedoraproject.org/t/bluetooth-a2dp-regression-in-bluez-5-83-5-84-connection-fails-on-startup-tp-link-ub500-plus/165055](https://discussion.fedoraproject.org/t/bluetooth-a2dp-regression-in-bluez-5-83-5-84-connection-fails-on-startup-tp-link-ub500-plus/165055)
* BlueZ upstream — GitHub Issue #1570: *A2DP connection fails on startup with BlueZ 5.83/5.84*
  [https://github.com/bluez/bluez/issues/1570](https://github.com/bluez/bluez/issues/1570)

Other similar or related reports:

* Red Hat Bugzilla — Bug 2374150: *Soundcore Q30 disconnects A2DP after update (bluez-5.83-1.fc42)*
  [https://bugzilla.redhat.com/show_bug.cgi?id=2374150](https://bugzilla.redhat.com/show_bug.cgi?id=2374150)
* BlueZ GitHub — Issue #1545: *A2DP devices disconnect immediately after connecting (PipeWire/WirePlumber race condition)*
  [https://github.com/bluez/bluez/issues/1545](https://github.com/bluez/bluez/issues/1545)