Created attachment 188727 [details] Powertop showing kdeconnectd high wake ups per second SUMMARY STEPS TO REPRODUCE 1. Boot up system, log in 2. Make sure package "powertop" is installed by package manager 3. Open terminal and run: sudo powertop 4. Leave system idle for a minute 5. Find /usr/bin/kdeconnectd on the event list OBSERVED RESULT Observe /usr/bin/kdeconnectd generates > 60 events per second EXPECTED RESULT Seems like a regression. Previously kdeconnectd was not on the top wake ups list at all. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 43 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION High amount of wake ups causes excessive power consumption and reduced battery life on laptops.
Tested on multiple systems and the issue is consistent. IMHO kdeconnectd should wake up the CPU to check connections far less than 60 times per seconds. Preferrably 1 or 2 times per second is enough, especially in the background. Any unnecessary wake ups would cause enery consumption and reduce run time for battery powered devices.
kdeconnectd is basically socket io based so if you see a high wakeup rate it means that kdeconnectd is processing incoming requests from remote devices or sending notifications/mpris events etc. Without knowing what you have configured and how many devices you have linked there is not a lot to investigate. For me with 4 connected devices kdeconnectd sits just above or below 10 wakeups per sec which is nothing compared to what firefox is doing
(In reply to Erik Duisters from comment #2) > kdeconnectd is basically socket io based so if you see a high wakeup rate it > means that kdeconnectd is processing incoming requests from remote devices > or sending notifications/mpris events etc. Without knowing what you have > configured and how many devices you have linked there is not a lot to > investigate. For me with 4 connected devices kdeconnectd sits just above or > below 10 wakeups per sec which is nothing compared to what firefox is doing I removed all other devices on the network, uninstalled KDE Connect application on my Android phone. Only leaving this single computer with KDE connectd running and it still generated 60 wake ups per second. Is there any where to inspect the opened sockets? logs? Killing kdeconnectd can make it calm down and I can easily gain an hour of run time off my laptop battery but I don't want to keep killing the process.
Created attachment 188746 [details] attachment-2893127-0.html If you start kdeconnectd in the foreground this way: QT_LOGGING_RULES=kdeconnect.*.debug=true /usr/bin/kdeconnectd You should get some debugging info On woensdag 21 januari 2026 10:27:47 Midden-Europese standaardtijd you wrote: > https://bugs.kde.org/show_bug.cgi?id=514881 > > Bo Zhang <ndawinteractive@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #3 from Bo Zhang <ndawinteractive@gmail.com> --- > (In reply to Erik Duisters from comment #2) > > > kdeconnectd is basically socket io based so if you see a high wakeup rate > > it means that kdeconnectd is processing incoming requests from remote > > devices or sending notifications/mpris events etc. Without knowing what > > you have configured and how many devices you have linked there is not a > > lot to investigate. For me with 4 connected devices kdeconnectd sits just > > above or below 10 wakeups per sec which is nothing compared to what > > firefox is doing > I removed all other devices on the network, uninstalled KDE Connect > application on my Android phone. Only leaving this single computer with KDE > connectd running and it still generated 60 wake ups per second. Is there > any where to inspect the opened sockets? logs? Killing kdeconnectd can make > it calm down and I can easily gain an hour of run time off my laptop > battery but I don't want to keep killing the process.
(In reply to Erik Duisters from comment #4) > Created attachment 188746 [details] > attachment-2893127-0.html > > If you start kdeconnectd in the foreground this way: > > QT_LOGGING_RULES=kdeconnect.*.debug=true /usr/bin/kdeconnectd > > You should get some debugging info The log doesn't have much. Nothing suspicious. No continuous stream of output. Just normal start up / connect / disconnect, etc. kdeconnectd keeps waking up 60 times per second during testing. Attached log: bo@x30w:~$ QT_LOGGING_RULES=kdeconnect.*.debug=true /usr/bin/kdeconnectd kdeconnect.core: Daemon starting kdeconnect.core: DBus registration complete kdeconnect.core: Constructing Backends kdeconnect.core: Constructed LanLinkProvider Backend kdeconnect.core: Constructed AsyncLinkProvider<AsyncLinkProvider> Backend kdeconnect.core: Backends loaded kdeconnect.core: Paired devices added kdeconnect.core: Broadcasting identity packet kdeconnect.core: Broadcasting as QHostAddress("192.168.1.74") kdeconnect.core: LanLinkProvider started kdeconnect.core: Link providers started kdeconnect.core: Daemon start completed kdeconnect.core: BluetoothLinkProvider::ctor executed kdeconnect.core: BluetoothLinkProvider::ctor finished kdeconnect.core: BluetoothLinkProvider::onStart executed kdeconnect.core: BluetoothLinkProvider::tryToInitialise re-setting up mBluetoothServer kdeconnect.core: BluetoothLinkProvider::tryToInitialise new mBluetoothServer completed kdeconnect.core: BluetoothLinkProvider::tryToInitialise About to start server listen kdeconnect.core: BluetoothLinkProvider::onStartDiscovery executed qt.bluetooth.bluez: Missing CAP_NET_ADMIN permission. Cannot determine whether a found address is of random or public type. kdeconnect.core: BluetoothLinkProvider::onStartDiscovery executed kdeconnect.core: TCP connection done (i'm the existing device) kdeconnect.core: Starting server ssl (I'm the client TCP socket) kdeconnect.core: Socket successfully established an SSL connection kdeconnect.core: Device discovered "cd98289b645d4f39b71cac97ceb3ee7c" via link with priority 20 kdeconnect.core: It is a known device "Find X8" kdeconnect.core: Not loading plugin "kdeconnect_remotecommands" because device doesn't support it kdeconnect.core: Not loading plugin "kdeconnect_virtualmonitor" because device doesn't support it kdeconnect.core: Not loading plugin "kdeconnect_lockdevice" because device doesn't support it kdeconnect.core: Not loading plugin "kdeconnect_remotesystemvolume" because device doesn't support it kdeconnect.core: Device "Find X8" status changed. Reachable: true . Paired: true kdeconnect.core: "Find X8" - reload plugins kdeconnect.core: Loaded plugin: "kdeconnect_notifications" kdeconnect.core: Loaded plugin: "kdeconnect_ping" kdeconnect.core: Loaded plugin: "kdeconnect_presenter" kdeconnect.core: Loaded plugin: "kdeconnect_clipboard" kdeconnect.core: Loaded plugin: "kdeconnect_battery" kdeconnect.core: Loaded plugin: "kdeconnect_sms" kdeconnect.core: Loaded plugin: "kdeconnect_findmyphone" kdeconnect.core: Loaded plugin: "kdeconnect_pausemusic" kdeconnect.core: Loaded plugin: "kdeconnect_mousepad" kdeconnect.core: Loaded plugin: "kdeconnect_remotecontrol" kdeconnect.core: Loaded plugin: "kdeconnect_connectivity_report" kdeconnect.core: Loaded plugin: "kdeconnect_telephony" kdeconnect.core: Loaded plugin: "kdeconnect_share" kdeconnect.core: Loaded plugin: "kdeconnect_remotekeyboard" kdeconnect.core: Loaded plugin: "kdeconnect_mmtelephony" kdeconnect.core: Loaded plugin: "kdeconnect_mprisremote" kdeconnect.core: Loaded plugin: "kdeconnect_mpriscontrol" kdeconnect.core: Loaded plugin: "kdeconnect_findthisdevice" kdeconnect.plugin.sftp: add to dolphin kdeconnect.plugin.sftp: Created device: "Find X8" kdeconnect.core: Loaded plugin: "kdeconnect_sftp" kdeconnect.core: Loaded plugin: "kdeconnect_systemvolume" kdeconnect.plugin.contacts: Contacts constructor for device "Find X8" kdeconnect.core: Loaded plugin: "kdeconnect_contacts" kdeconnect.plugin.contacts: sendRequest: Sending "kdeconnect.contacts.request_all_uids_timestamps" true kdeconnect.core: Loaded plugin: "kdeconnect_runcommand" qt.bluetooth.bluez: No uuids found for "22:22:A4:BC:50:AF" kdeconnect.core: BluetoothLinkProvider::onStartDiscovery executed kdeconnect.core: LanLinkProvider deviceLinkDestroyed "cd98289b645d4f39b71cac97ceb3ee7c" kdeconnect.core: "Find X8" - reload plugins kdeconnect.core: Device "Find X8" status changed. Reachable: false . Paired: true kdeconnect.core: BluetoothLinkProvider::onStartDiscovery executed
Tested on KDE 6.4.3 and it is not happening. Same network, same connected devices. There is no CPU wake-ups from kdeconnectd on KDE 6.4.3. So definitely a regression on 6.5. Seems as if it is actively polling something.