[kdeconnect] [Bug 344432] SFTP: When attempting to view kdeconnect in dolphin it crashes
https://bugs.kde.org/show_bug.cgi?id=344432 Sunhoo changed: What|Removed |Added CC||sun...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 344432] SFTP: When attempting to view kdeconnect in dolphin it crashes
https://bugs.kde.org/show_bug.cgi?id=344432 --- Comment #3 from Sunhoo --- I can confirm the same exact bug on the latest KDE Neon User Edition (and it's been that way for months). I built kdeconnect from source and started it from command line, here's what logs I've got for the daemon kdeconnectd: kdeconnect.core: KdeConnect daemon starting kdeconnect.core: onStart kdeconnect.core: KdeConnect daemon started kdeconnect.core: Broadcasting identity packet kdeconnect.core: Socket connected QSslSocket(0xe51ba0) kdeconnect.core: TCP connection done (i'm the existing device) kdeconnect.core: Starting server ssl (I'm the client TCP socket) kdeconnect.core: Socket succesfully stablished an SSL connection kdeconnect.core: It is a known device "Motorola" kdeconnect.core: Not loading plugin "kdeconnect_remotecommands" because device doesn't support it Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kdeconnect.plugin.sftp: add to dolphin kdeconnect.plugin.sftp: Created device: "Motorola" QObject::connect: No such signal QDBusAbstractInterface::messageReceived(QString,QString) [1]25814 segmentation fault build/daemon/kdeconnectd (Sometimes it also says: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) before the segfault.) And for kdeconnect-indicator: kdeconnect.interfaces: Adding missing or previously removed device "9a8b63987a327f12" kdeconnect.interfaces: Adding missing or previously removed device "9a8b63987a327f12" kdeconnect.interfaces: dbus interface not valid kdeconnect.interfaces: dbus interface not valid kdeconnect.interfaces: dbus interface not valid kdeconnect.interfaces: dbus interface not valid kdeconnect.interfaces: Adding missing or previously removed device "9a8b63987a327f12" kdeconnect.interfaces: Adding missing or previously removed device "9a8b63987a327f12" kdeconnect.interfaces: Adding missing or previously removed device "9a8b63987a327f12" kdeconnect.interfaces: dbus interface not valid The daemon segfaults and crashes automatically once it finds the device (before I can even launch dolphin and try to browse). It doesn't crash like that with the official package from KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 344432] SFTP: When attempting to view kdeconnect in dolphin it crashes
https://bugs.kde.org/show_bug.cgi?id=344432 --- Comment #4 from Sunhoo --- I found the sshfs command used by the kdeconnect daemon to try to mount the device: sshfs kdeconnect@10.20.10.10:/ /home/jean/.config/kdeconnect/9a8b63987a327f12/kdeconnect_sftp/9a8b63987a327f12 -p 1739 -f -F /dev/null -o IdentityFile=/home/jean/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss -o password_stdin Except that 10.20.10.10 is my tun0 address and it should be using 192.168.0.41 which is my local network address (from wlan0, which is what I'd use when I manually ssh into my device). So when I execute this command manually, it just hangs for 60 seconds then timeout as expected. But if I change the command to: sshfs kdeconnect@192.168.0.41:/ /home/jean/.config/kdeconnect/9a8b63987a327f12/kdeconnect_sftp/9a8b63987a327f12 -p 1739 -f -F /dev/null -o IdentityFile=/home/jean/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss -o password_stdin -d I get: FUSE library version: 2.9.7 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 Warning: Permanently added '[192.168.0.41]:1739' (DSA) to the list of known hosts. Permission denied (password). read: Connection reset by peer It waits for the password from the standard input (see "-o password_stdin"), so I enter something then it does seem to find the device but the connection is denied because of the incorrect password. This is normal since this password should be automatically given by KDE Connect and we are not supposed to type it in. So how come 10.20.10.10 is used instead of 192.168.0.41 (in my case)? As a side note, I do use a VPN on both devices but the result is the same when not connected to them. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 344432] SFTP: When attempting to view kdeconnect in dolphin it crashes
https://bugs.kde.org/show_bug.cgi?id=344432 --- Comment #5 from Sunhoo --- After some debugging, I can see that the problem (in my case at least) does come from my smartphone's VPN: it creates a tun0 interface to which KDE Connect tries to connect but can't. For example the VPN creates tun0 with an address of 10.20.10.10 and my wlan0 address is 192.168.0.41. The address sent by the KDE Connect app is 10.20.10.10 and this is where the connection timeout. If I hard code "192.168.0.41" for the network address in the KDE Connect source code, I can mount and browse the filesystem. I guess a solution in my case would be to redirect traffic from tun0 to wlan0 with iptables in Android. -- You are receiving this mail because: You are watching all bug changes.
