https://bugs.kde.org/show_bug.cgi?id=517743
--- Comment #12 from Anton <[email protected]> --- (In reply to Anton from comment #11) > I have the same problem. > It seems it happens after laptop goes into a sleep mode... > ------------------------------- > - OS: KDE neon User Edition, based on Ubuntu 24.04 Noble > - Kernel: Linux 7.0.0-28-generic > - Architecture: x86_64 > - CPU: Intel Core i7-9750H @ 2.60GHz > - CPU cores/threads: 6 cores, 12 threads > - RAM: 31 GiB total, 26 GiB available > - Swap: none configured > - GPUs: > - Intel UHD Graphics 630 > - NVIDIA GeForce GTX 1660 Ti Mobile I asked to prepare some info and logs about situation ------------------------------------------------------------------------------- # kdeconnectd high CPU / repeated Bluetooth UUID lookup failures ## Summary `kdeconnectd` was observed using ~100% of one CPU core until it was killed manually. The journal shows repeated Bluetooth/UUID discovery failures from `kdeconnectd`, especially for the same nearby Bluetooth addresses. This looks like KDE Connect may be repeatedly probing Bluetooth devices that have no UUIDs available. Command: ```bash sed -n '1,220p' ~/.config/kdeconnect/trusted_devices ``` Relevant output: ```ini [099f7fad_da50_4400_b31e_3aec7396731f] name=Pixel 8 Pro protocolVersion=8 type=phone ``` ## Current KDE Connect process/unit state after killing kdeconnectd Command: ```bash systemctl --user list-units --all '*kdeconnect*' ``` Output: ```text UNIT LOAD ACTIVE SUB DESCRIPTION [email protected] loaded inactive dead KDE Connect 1 loaded units listed. ``` Command: ```bash systemctl --user status kdeconnectd.service ``` Output: ```text Unit kdeconnectd.service could not be found. ``` ## Repeated failure seen in journal Command: ```bash journalctl --user --since '2026-07-25 17:00:00' --until '2026-07-25 19:20:00' _COMM=kdeconnectd ``` Relevant output: ```text Jul 25 17:21:20 user-pc kdeconnectd[92570]: No uuids found for "E0:9D:13:6B:58:13" Jul 25 17:42:20 user-pc kdeconnectd[92570]: No uuids found for "E0:9D:13:6B:58:13" Jul 25 17:43:20 user-pc kdeconnectd[92570]: No uuids found for "E0:9D:13:6B:58:13" Jul 25 17:45:20 user-pc kdeconnectd[92570]: No uuids found for "E0:9D:13:6B:58:13" ... repeated for a long time ``` ## Recurrence over recent journal history Command: ```bash journalctl --user --since '2026-07-18 00:00:00' --grep 'No uuids found' --no-pager -o cat | wc -l ``` Output: ```text 641 ``` Command: ```bash journalctl --user --since '2026-07-18 00:00:00' --grep 'No uuids found' --no-pager -o cat \ | awk -F'"' '{count[$2]++} END {for (mac in count) print count[mac], mac}' \ | sort -nr \ | sed -n '1,20p' ``` Output: ```text 334 F4:14:BF:B8:0A:09 196 E0:9D:13:6B:58:13 9 24:75:3A:0E:C1:AC 7 EC:ED:04:B7:06:32 ... ``` ## Other related startup warnings Command: ```bash journalctl --user --since today | grep -i kdeconnect ``` Relevant output: ```text Jul 25 09:47:21 user-pc baloo_file[2442]: Failed to get list of devices: "No such object path '/modules/kdeconnect'" Jul 25 15:23:10 user-pc plasmashell[2613]: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/modules/kdeconnect/devices/099f7fad_da50_4400_b31e_3aec7396731f/notifications'") Jul 25 15:23:10 user-pc kscreenlocker_greet[92556]: Failed to get list of devices: "No such object path '/modules/kdeconnect'" Jul 25 15:23:40 user-pc kdeconnectd[92570]: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type. ``` ## Bluetooth devices known to the system Command: ```bash bluetoothctl devices ``` Output: ```text Device 80:99:E7:2D:6C:19 WH-1000XM4 ``` ## Notes - `kdeconnectd` was killed manually after it was seen using ~100% of one CPU core. - The journal does not explicitly log the CPU usage, but it does show repeated UUID lookup failures from `kdeconnectd` before the process was killed. - The repeated addresses do not match the only known paired Bluetooth device from `bluetoothctl devices`. - The most suspicious pattern is the repeated `No uuids found for "<MAC>"` messages from `kdeconnectd`, recurring hundreds of times over recent journal history. -- You are receiving this mail because: You are watching all bug changes.
