Bug 506319

Summary:	Bluetooth headset keeps disconnecting from my computer after the bluetooth backend of kdeconnect is enabled
Product:	[Applications] kdeconnect	Reporter:	sunliwei2015s
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	REPORTED ---
Severity:	normal	CC:	andrew.g.r.holmes, heri+kde, kde, notsyncing
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description sunliwei2015s 2025-06-28 17:00:28 UTC

SUMMARY
When the bluetooth backend of KDE Connect is enabled, my bluetooth headset will automatically disconnect from my computer after roughly 4 seconds. Disabling the bluetooth backend and then rebooting the computer resolves this issue.

STEPS TO REPRODUCE
1. Enable the bluetooth backend of kdeconnect.
2. Connect to a bluetooth headset
3. Wait for several seconds

OBSERVED RESULT
The bluetooth headset disconnects from the computer.

EXPECTED RESULT
The bluetooth headset should continue to work normally.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

Comment 1 notsyncing 2025-07-25 04:54:20 UTC

Same here on KDE plasma 6.4.3, frameworks 6.16.0, qt 6.9.1

After disabling the bluetooth backend of kde connect, my bluetooth headset no longer auto disconnects.

Comment 2 Hugh Redman 2025-12-02 11:41:46 UTC

I'm experiencing the same issue with KDE Plasma Version 6.5.3, KDE Frameworks 6.20.0 and  KDE Connect 25.08.3 running on Nobara 43 with BlueZ 5.83 and higher (early versions of BlueZ don't exhibit the same issue).

When the KDE Connect Bluetooth backend is enabled, multiple Authentication requests are sent to the device, seconds apart, the first of which succeeds but the second of which fails, in BlueZ 5.83 and higher the failed authentication request causes the device to be disconnected. Several examples are available in this issue on the BlueZ github: https://github.com/bluez/bluez/issues/1545

Changed BlueZ behaviour appears to be tied to https://github.com/bluez/bluez/commit/00969bdb17ea01af8722d5bdcf8b2c19e06e9456 however I would expect that the correct behaviour is to not generate authentication requests that will fail rather than letting devices that fail auth requests to remain connected.