I’m noticing that there’s two entries for my phone in the LHS pane under Dolphin under ‘Devices’, and at times Dolphin seems to hang with KDE Connect loading one core at 100% utilization. If I open Htop and kill KDE Connect everything goes back to normal.
Anyone else experiencing this?
Yes, I also have a freeze, but here when I right click on files to open the context menu, if I run Dolphin on a terminal; it tells:
kf.solid.backends.kdeconnect: Failed to get list of devices: "Did not receive a reply. Possible causes include: the remote application did n
ot send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
running
$ killall kdeconnectd
give me back the possibility to right click on files.
I have the same problem here, when the issue occurs I can’t right click on files. Killing KDE connect overcomes the problem and allows me to right click on files again.
Relevant bug report:
The issue seams to have randomness part of it: for a week or so (on KDE Neon User Edition up to date) I could use the OS daily and Dolphin without having to kill kdeconnectd a single time.
But yesterday, the locked “right-click” on a file in Dolphin got triggered again, and I had to kill the process to workaround.
It’s been a constant annoyance here, I really wish we could get this bug resolved. The right click under Dolphin no longer seems to be an issue, but every now and then I open htop and in 8 out of 10 times kdeconnectd is using 100% of one core.
You can tell, as thermal monitor shows CPU temps increasing slightly.
After weeks, I had to adapt my workflow and learn to live with it. Yes, extremely annoying freeze on something really common like right-clicking on a file.
I’m sharing here a little Bash script and launcher that improved my quality of life with KDE Neon and this bug. Note: it use notify-send as a library, probably part of a package named libnotify something. It is to display a notification in the corner of the screen.
I saved this one as toggle-kdeconnectd.sh and gave it permission to execute with a right-click, properties, permissions:
#!/bin/bash
Check if kdeconnectd is running and toggle it
is_running=$(pgrep -x kdeconnectd)
if [ -n "$is_running" ]; then
Process is running, kill it
kill "$is_running"
notify_message="kdeconnectd has been stopped"
else
Process is not running, start it
kdeconnectd &
notify_message="kdeconnectd has been started"
fi
Send notification
notify-send "KDE Connect" "$notify_message"
I also created a launcher to it in /home/<yourusername>/.local/share/applications/ with a toggle-kdeconnectd.desktop like this (adapt the path of the icon and script) :
[Desktop Entry]
Categories=Utility;System;
Comment[en_US]=Start or stop KDE Connect daemon
Comment=Start or stop KDE Connect daemon
Exec=/home/<yourusername>/toggle-kdeconnectd.sh
GenericName[en_US]=
GenericName=
Icon=/home/<yourusername>/toggle-kdeconnectd.svg
MimeType=
Name[en_US]=Toggle KDE Connect
Name=Toggle KDE Connect
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=
And the custom icon (svg):
Usage:
When the freeze happens, just open the main menu, and if you put the software “toggle-kdeconnectd” in your fav, just click the icon. Done.
If you need Kdeconnect to transfer file from your mobile or anything, just run it again, it will restore the process.
For me this only happened so far when I (and my phone) left the building (and thus the Wifi) or when I return (can’t really tell which of the two changes triggers it).
But then it triggers consistently
It’s happening all the time here, whether I leave home with my phone and return or not. It’s actually becoming really annoying.
Where is the bugfix 6.7.1 release for KDE Neon?
Confirming the same bug. Noticing the lockups by the CPU temp spiking up and staying there. Agreed, rather annoying one…
I received the update to KDE Neon 6.7.2 this morning, I was hoping it would resolve the kdeconnectd issue, sadly it hasn’t. This is really annoying, almost every time I check htop, kdeconnectd is loading a core 100% and I have to manually kill the process to regain a core.
Having this same issue on neon :< might just disable kde connect for a bit, sucks but it keeps my laptop pegged at max fan speed all the time for no reason!
KDE Neon 6.7.3 - still not resolved 
It’s really annoying, as soon as the phone goes out of WiFi range, KDE Connect hogs one core to itself 100% and you can’t right click anything.
