I’m running KDE Connect 21.12.3-0ubuntu1 on an Ubuntu 22.04 laptop.
After resuming my laptop from sleep and restarting its network connection, the KDE Connect GUI reports ‘No devices found…’, although it worked before sleep.
A number of other KDE Connect devices are available on the network, pingable, and I’ve checked the port in use TCP 1716 is open on my machine.
~$ sudo netstat -tunelp | grep -i kdeconnect
tcp6 0 0 :::1716 :::* LISTEN 1000 4496511 16319/kdeconnectd
udp6 0 0 :::1716 :::* 1000 4495692 16319/kdeconnectd
~$ nmap -p 1716 192.168.xxx.xxx
Starting Nmap 7.80 ( https://nmap.org ) at 2025-01-03 13:09 GMT
Nmap scan report for ********* (192.168.xxx.xxx)
Host is up (0.00036s latency).
KDE Connect also no longer reports ‘previously connected devices’, just a blank screen.
Quit and restart from the GUI doesn’t change this.
I couldn’t find command line commands to restart kdeconnectd; eventually I killed it and restarted with
$ /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
Systemctl doesn’t seem to know about it - is there a man page for kdeconnectd?
Any ideas what might be causing the problem or how to troubleshoot it?
Thanks!
Hi! I believe kdeconnectd gets started from an XDG autostart file, which is started by systemd but I don’t believe is managed by it from that point forward (at least in the same way as other services).
It looks like you have some of the network diagnostic steps already in use from KDEConnect - KDE UserBase Wiki , so I wonder if at this point it would be helpful to try starting from a clean slate on that device, as mentioned there, by stopping KDE Connect, moving the ~/.config/kdeconnect file to a backup, and running the application again?
And just to check, are the other devices on newer versions of KDE Connect? I can’t verify personally, but it could be possible that there might be some more glitches when dealing with versions that are pretty far apart - a system running the latest upstream software would have a version almost three years newer than the one installed on that laptop.
There has also been a bug report about a similar-sounding situation: 477670 – KDEConnect is unable to connect to paired devices after sleep It might be worth checking to see if merely switching your network connection and then switching back, without putting the device into sleep, also reproduces the issue?
Thanks
Other devices are Android, and a MacBook Air on the recent Osx version, so presumably newer.
The autostart file was
org.kde.kdeconnect.daemon.desktop
in /etc/xdg/autostart/
which runs
/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
I backed up > ~/.config/kdeconnect
killed and restarted kdeconnect.
After re-pairing devices I was able to send files from one device to my laptop, also after changing my laptop’s network connection from wireless to wired. However the Plug-in settings - Share and Receive ‘properties’ which allows selection of destination folder isn’t available, and there’s no notification to show a file is being received, although there was for a ping.
I tried sleep mode, briefly, and it has reconnected, so perhaps it is now fixed - other than the Plug-in Setings and notifications - as this has been a bugbear ever since I first used KDE Connect.