Bug 513461

Summary: kdeconnectd logspam: "Cannot find Bluez 5 adapter for device search false"
Product: [Applications] kdeconnect Reporter: Jonathan Teh <jonathan.teh>
Component: desktop-applicationAssignee: Albert Vaca Cintora <albertvaka>
Status: CONFIRMED ---    
Severity: normal CC: johnparmitage, lingm+kdebugs, mundolibre, smowtenshi
Priority: NOR    
Version First Reported In: 25.12.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jonathan Teh 2025-12-17 01:27:47 UTC
SUMMARY
Every 30s, kdeconnectd logs this to the system log, from `journalctl -b`:

Dec 17 00:20:03 hostname kdeconnectd[2707]: Cannot find Bluez 5 adapter for device search false
Dec 17 00:20:33 hostname kdeconnectd[2707]: Cannot find Bluez 5 adapter for device search false
Dec 17 00:21:03 hostname kdeconnectd[2707]: Cannot find Bluez 5 adapter for device search false
Dec 17 00:21:33 hostname kdeconnectd[2707]: Cannot find Bluez 5 adapter for device search false

This started happening after Fedora 43 upgraded to KDE Gear 25.12.0 + KDE Plasma 6.5.4 + KDE Frameworks 6.21 in https://bodhi.fedoraproject.org/updates/FEDORA-2025-e2d6cf1cf4. The system is a desktop without any Bluetooth adapters.

These are the log entries for kdeconnectd leading up to the logspam:

Dec 16 23:54:03 hostname kdeconnectd[2707]: Cannot find a compatible running Bluez. Please check the Bluez installation. QtBluetooth requires at least BlueZ version 5.
Dec 16 23:54:03 hostname kdeconnectd[2707]: No local bluetooth adapter found
Dec 16 23:54:03 hostname kdeconnectd[2707]: No Primary Battery detected on this system. This may be a bug.
Dec 16 23:54:03 hostname kdeconnectd[2707]: Total quantity of batteries found:  0
Dec 16 23:54:03 hostname kdeconnectd[2707]: Primary Battery seems to have been removed. Suspending packets until it is reconnected.
Dec 16 23:54:03 hostname kdeconnectd[2707]: No object for name "alsa_output.pci-0000_09_00.6.analog-stereo.monitor"
Dec 16 23:54:04 hostname kdeconnectd[2863]: QThreadStorage: entry 2 destroyed before end of thread 0x55c8852620b0
Dec 16 23:54:04 hostname kdeconnectd[2863]: QThreadStorage: entry 1 destroyed before end of thread 0x55c8852620b0
Dec 16 23:54:04 hostname kdeconnectd[2707]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Dec 16 23:54:33 hostname kdeconnectd[2707]: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
Dec 16 23:54:33 hostname kdeconnectd[2707]: Cannot find Bluez 5 adapter for device search false

The first line on "Cannot find a compatible running Bluez" seems to have always been there, the relevant packages are installed:

bluedevil-6.5.4-1.fc43.x86_64
bluez-5.85-1.fc43.x86_64
bluez-libs-5.85-1.fc43.x86_64
bluez-obexd-5.85-1.fc43.x86_64
bluez-cups-5.85-1.fc43.x86_64
bluez-libs-5.85-1.fc43.i686
kf5-bluez-qt-5.116.0-4.fc43.x86_64
kf6-bluez-qt-6.21.0-1.fc43.x86_64

STEPS TO REPRODUCE
1. Log in to a KDE session with kdeconnectd installed.
2. Run `journalctl -b`.
3. 

OBSERVED RESULT
Logspam every 30s as shown above.

EXPECTED RESULT
No logspam.

SOFTWARE/OS VERSIONS
Linux: Fedora 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Workaround is to disable the Bluetooth backend in kdeconnectd then the logspam stops but this has to be done for every user.
A similar bug was raised in https://bugs.kde.org/show_bug.cgi?id=417421 but that log entry ends in "device search true" instead.
Comment 1 David Marzal 2026-01-16 20:29:27 UTC
ame problem with ArchLinux:
I do have a Bluetooth adapters (but bluetooth.service disabled), and the BT option disabled on KDEconnect 

Similar report on the web:
https://forum.manjaro.org/t/i-see-a-heap-of-bluetooth-stuff-in-the-logs/184158/9
https://discussion.fedoraproject.org/t/cannot-find-bluez-5-adapter-for-device-search-false/179401

Logs:
kdeconnectd[1486]: Cannot find a compatible running Bluez. Please check the Bluez installation. QtBluetooth requires at least BlueZ version 5.
kdeconnectd[1486]: No local bluetooth adapter found
kdeconnectd[1718]: QThreadStorage: entry 2 destroyed before end of thread 0x9e82e9f4d50
kdeconnectd[1718]: QThreadStorage: entry 1 destroyed before end of thread 0x9e82e9f4d50
kdeconnectd[1486]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
kdeconnectd[1486]: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type.
kdeconnectd[1486]: Cannot find Bluez 5 adapter for device search false
....
Comment 2 Jonathan Teh 2026-01-17 00:15:59 UTC
Since Fedora 43 upgraded to KDE Gear 25.12.1 + KDE Frameworks 6.22 in  https://bodhi.fedoraproject.org/updates/FEDORA-2026-dab67734c1, the workaround of disabling the Bluetooth backend in kdeconnectd does not persist across sessions. The next time kdeconnectd starts, this message:

Jan 17 00:06:39 hostname kdeconnectd[5017]: Cannot find Bluez 5 adapter for device search false

is logged every 30s again. Checking the KDE Connect settings via the tray icon shows that the Bluetooth backend is disabled but it has to be toggled i.e. enabled then disabled again to stop those messages. This now has to be done at every login.
Comment 3 Jonathan Teh 2026-02-08 15:47:03 UTC
Fedora 43 upgraded to KDE Gear 25.12.2 in https://bodhi.fedoraproject.org/updates/FEDORA-2026-855f57493d.
No change in behaviour to 25.12.1, the Bluetooth backend has to be toggled i.e. enabled then disabled again to stop these messages at every login.