https://bugs.kde.org/show_bug.cgi?id=514881
--- Comment #4 from Erik Duisters <[email protected]> --- 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 <[email protected]> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |--- > Status|NEEDSINFO |REPORTED > > --- Comment #3 from Bo Zhang <[email protected]> --- > (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. -- You are receiving this mail because: You are watching all bug changes.
