| Summary: | KDEConnect fails to open remote phone directory as it says protocol died unexpectedly | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Andras <andrasszerencses1> |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | 288pat0tem, 988alex, anderslgade, andrasszerencses1, arcooke, boingo-00, dellfirmware, e.duisters1, erasmocaponio, flareload, info, j12, jelmorini, rikmills, tommybeauclair, tonal.promsoft, vanush.kamaryan, wcbrow02 |
| Priority: | NOR | ||
| Version: | 1.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/kdeconnect-kde/8388ed0603f0d04d7adde2152b077dbd29275ee3 | Version Fixed In: | 1.3.3 |
| Sentry Crash Report: | |||
| Attachments: | dolphin after some F5 | ||
|
Description
Andras
2018-10-23 04:27:13 UTC
(In reply to Andras from comment #0) > SOFTWARE VERSIONS > (available in About System) > KDE neon 5.14 > KDE Plasma Version: 5.14.1 > KDE Frameworks Version: 5.51.0 > Qt Version: 5.11.2 > Kernel Version: 4.15.0-36-generic > OS Type: 64-bit > I have same problem. Phone: Meizu M3, Android 5.1, Flyme 7.8.7.24 beta *** Bug 399943 has been marked as a duplicate of this bug. *** *** Bug 399998 has been marked as a duplicate of this bug. *** Could those who are affected by this please do the following: After experiencing the error, run the command: qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp isMounted And report whether that returns true or false, then run qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp mountAndWait Wait for the command to return, then check if browsing the phone through Dolphin works as expected In the above commands, <deviceID> needs to be replaced with your actual device ID. This can be checked by running `kdeconnect-cli --list-devices` If you don't have qdbus installed, any other dbus-poking program is equally useful. The GUI programs qdbus-qt5 and d-feet are nice too. For me, results for given commands above on two different PC with the same installation and with beta participation on Google's Play Store: qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp isMounted false qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp mountAndWait Browsing the phone through Dolphin still won't work qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp isMounted true > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp > isMounted true > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp > mountAndWait 0 files in dolphin Well darn. I thought for sure that was the problem. If I think of something else to try, I will post again. I have the same problem with kdeconnect, isMounted and mountAndWait return both true. But I found that executing the command with getDirectories gives me the correct path all mounted directories of the devices (/run/user/1000/<device ID>/storage/emulated/0). I'm also able to access the directories and modify files in it. > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp > isMounted true > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp > mountAndWait 0 files in dolphin Same here > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/98376001b1d01cc3/sftp isMounted true > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/98376001b1d01cc3/sftp mountAndWait true > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/98376001b1d01cc3/sftp isMounted true Empty directory in dolphin. But after F5 - 2 entry: "all files" and "photos". After each F5 press add also "photos". Created attachment 115884 [details]
dolphin after some F5
(In reply to Alexandr Zamaraev (aka Tonal) from comment #11) > Created attachment 115884 [details] > dolphin after some F5 If it's a suggestion to use F5 well, you can see it's not that simple problem that someone just forgot to refresh something. Thanks anyways. I have the same problems with kdeconnect see the bug report I opened under https://bugs.kde.org/show_bug.cgi?id=399943 I have verified this with two KDE Neon installations, both show the same error behavior. regards Michael Experienced only in KDE Neon, other distros and Kubuntu is fine. kdeconnect-cli --list-devices - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) 1 device found qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted true qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait true Error : The process for the kdeconnect://104bfb976bc224ee protocol died unexpectedly. Checked in terminal, and it seems to be mounted and can be browsed: kdeconnect@192.168.0.103:/ 1048576000 0 1048576000 0% /run/user/1001/104bfb976bc224ee Even with the path pasted to Dolphin. Issue not fixed in Neon User ed. by the 5.14.2 update installed today. Kubuntu 18.10 (with backports) on the same Plasma version is fine. I quote the Comments #14 and #15 of Laosom (neon 5.14.1 and 5.14.2). I don't know about other distros. I can also confirm the issue on KDE Neon 5.14.2 with Dell XPS-13 and the device Google Pixel 1 with Android 9 (I don't know though if Kdeconnect depends on the Android version). It looks like there is a common thread in these issues that everyone is running some Ubuntu-based distribution Could everyone who is affected by this problem please post: - The result of running the two dbus commands I describe in comment 4: https://bugs.kde.org/show_bug.cgi?id=400178#c4 - Whether or not you are able to manually navigate to the mount point and browse the phone filesystem after running the above dbus commands You can find the mount point(s) by running `qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp getDirectories` - Your system version information, as in the very first comment. Especially, make sure to include your distro and version (but all the other information might be helpful too) Sorry that I don't have better news for you. Hopefully we can get to the bottom of this. For me it's even worse now as it was on my comment #5 above: https://bugs.kde.org/show_bug.cgi?id=400178#c5 Previously it's mounted, now it won't mount either: qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp mountAndWait false I'm not sure if it's count, I found these line during the process through jurnalctl -ex for example: kdeconnect.plugin.sftp: Timeout: device not responding gdk_device_update_tool: assertion 'GDK_IS_DEVICE (device)' failed UdevQt: unhandled device action "unbind" Hello Simon Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.2 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.15.0-38-generic OS Type: 64-bit Processors: 2 × Intel® Core™2 Duo CPU P8400 @ 2.26GHz Memory: 3,8 GiB of RAM $ kdeconnect-cli --list-devices - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) 1 device found $ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted true $ df -h Filesystem Size Used Avail Use% Mounted on udev 1,9G 0 1,9G 0% /dev tmpfs 390M 1,5M 389M 1% /run /dev/sda6 12G 11G 916M 92% / tmpfs 2,0G 15M 1,9G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 2,0G 0 2,0G 0% /sys/fs/cgroup /dev/loop0 88M 88M 0 100% /snap/core/5328 /dev/loop1 88M 88M 0 100% /snap/core/5548 /dev/loop2 88M 88M 0 100% /snap/core/5662 tmpfs 390M 16K 390M 1% /run/user/1000 kdeconnect@192.168.0.103:/ 1000G 0 1000G 0% /run/user/1000/104bfb976bc224ee $ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait true $ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp getDirectories /run/user/1000/104bfb976bc224ee/storage/extSdCard: SD card /run/user/1000/104bfb976bc224ee/storage/extSdCard/DCIM/Camera: Camera pictures(SD card) /run/user/1000/104bfb976bc224ee/storage/sdcard0: Internal storage /run/user/1000/104bfb976bc224ee/storage/sdcard0/DCIM/Camera: Camera pictures(Internal storage) journalctl -ex
okt 29 12:52:32 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: TCP connection done (i'm the existing device)
okt 29 12:52:32 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: Starting server ssl (I'm the client TCP socket)
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: Socket succesfully stablished an SSL connection
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: It is a known device "Samsung GT-S7710"
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: add to dolphin
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Created device: "Samsung GT-S7710"
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
okt 29 12:52:33 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sendnotification: Registered notifications listener for device "Samsung GT-S7710"
okt 29 12:52:41 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount device: "Samsung GT-S7710"
okt 29 12:52:41 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Created mounter
okt 29 12:52:41 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Starting loop to wait for mount
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Unmount QObject(0x0)
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.core: Converting IPv6 QHostAddress("::ffff:192.168.0.103") to IPv4 QHostAddress("192.168.0.103")
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Starting process: "sshfs kdeconnect@192.168.0.103:/ /run/user/1000/104bfb976bc224ee -p 1739 -s -f -F /
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in parameter list:
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Process started
okt 29 12:52:42 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: "Samsung GT-S7710" "Remote filesystem mounted at /run/user/1000/104bfb976bc224ee"
okt 29 12:52:43 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: stdout: "Warning: Permanently added '[192.168.0.103]:1739' (DSA) to the list of known hosts.\r\n"
okt 29 12:52:44 neonlts org.kde.kdeconnect[1453]: kf5.kio.widgets: KRun(0x55c2f22c0780) ERROR 143 "The process for the kdeconnect://104bfb976bc224ee protocol died unexpectedly."
okt 29 12:53:31 neonlts dbus-daemon[1453]: [session uid=1000 pid=1453] Activating service name='org.kde.runners.baloo' requested by ':1.24' (uid=1000 pid=1566 comm="/usr/bin/pla
okt 29 12:53:31 neonlts dbus-daemon[1453]: [session uid=1000 pid=1453] Successfully activated service 'org.kde.runners.baloo'
okt 29 12:54:45 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount device: "Samsung GT-S7710"
okt 29 12:59:22 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount device: "Samsung GT-S7710"
okt 29 12:59:58 neonlts org.kde.kdeconnect[1453]: kdeconnect.plugin.sftp: Mount device: "Samsung GT-S7710"
okt 29 13:00:00 neonlts org.kde.kdeconnect[1453]: kf5.kio.widgets: KRun(0x55c2f2223160) ERROR 143 "The process for the kdeconnect://104bfb976bc224ee protocol died unexpectedly."
Does running kdeconnectd under gdb give any extra output? $ killall $ gdb /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd the 'run' at the (gdb) prompt. (In reply to Laosom from comment #21) > journalctl -ex Forget it if I'm wrong however I don't think placing whole bunch of common device and journalctl information would help the thread, it creates a mess. (In reply to Andras from comment #23) > (In reply to Laosom from comment #21) > > journalctl -ex > > Forget it if I'm wrong however I don't think placing whole bunch of common > device and journalctl information would help the thread, it creates a mess. Sorry. (In reply to Laosom from comment #24) > Sorry. Now I feel bad. Although this place not for personal dialogue, excuse me if I was pedantic. I'd stuck with shorter posts but more info better than nothing and thanks for your comment Laosom. These are the results of the suggested commands: nicola@nicola-XPS-13-9360:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<device>/sftp isMounted false nicola@nicola-XPS-13-9360:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<device>/sftp mountAndWait true After the second command I still can't browse my phone content. This impacts me too, but I think I found a workaround? >qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp isMounted true >qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp mountAndWait true After running both of those I couldn't browse files via clicking "Phone" Dolphin or via the kde-connect browse-folder button. But I ran >qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp getDirectories and was able to `cd` to the directory reported and ls files there. On a whim, I copied the path into Dolphin and was able to browse my phone, open there as per normal. Opening and deleting also worked. So it *seems* like the issue is kde-connect's integration with eg Dolphin instead of a problem with the underlying storage mapping. System info: Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.2 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.15.0-38-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-3930K CPU @ 3.20GHz Memory: 15.6 GiB of RAM ERROR "The process for the kdeconnect://5254d9885e6b1ae0 protocol died unexpectedly." Happens when pressing the browse button on the KDEConnect Indicator and when trying to access through Dolphin. SYSTEM SPECIFICATIONS Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-38-generic OS Type: 64-bit Processors: 4 × Intel® Core™i7-7567U CPU@ 3.50GHz Memory: 15,6 GiB of RAM Phone: Nexus 5x YOUR REQUESTED ACTIONS qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp isMounted true qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp mountAndWait true I can manually navigate the mount point through the terminal ^ I also pasted the path into Dolphin and could successfully copy files to the phone, which prompted a notification from the KDEConnect indicator stating the file had been successfully copied to the device For me the results for the requested commands are:
qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp isMounted --> false
qdbus org.kde.kdeconnect /modules/kdeconnect/devices/<deviceID>/sftp mountAndWait --> true
> Wait for the command to return, then check if browsing the phone through Dolphin works as expected
Now I can see the folder structure and access the files via dolphin.
I use KDE Neon in fresh installation (bionic) updated (30.10.2018)
Betriebssystem: KDE neon 5.14
KDE-Plasma-Version: 5.14.2
Qt-Version: 5.11.2
KDE-Frameworks-Version: 5.51.0
Kernel-Version: 4.15.0-38-generic (buildd@lcy01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP
Art des Betriebssystems: 64-bit
Prozessoren: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Speicher: 31,4 GiB Arbeitsspeicher
NVIDIA GeForce GTX 1070/PCIe/SSE2 OpenGL 4.6.0 NVIDIA 396.54
with a Samsung S7 and a Samsung A3
Those who allegedly able to mount and access phone directories manually, please report your Kdeconnect version too. I was just hilariously frustrated why the hack it won't work for me till I just got kdeconnect 1.3.2 upgrade from 1.3.1. Now my results are: qdbus org.kde.kdeconnect /modules/kdeconnect/devices/0d78094f9d46e0b2/sftp isMounted false qdbus org.kde.kdeconnect /modules/kdeconnect/devices/0d78094f9d46e0b2/sftp mountAndWait true qdbus org.kde.kdeconnect /modules/kdeconnect/devices/0d78094f9d46e0b2/sftp isMounted true Now, I also able to reach phone directories through /run/user/1000/... with Kdeconnect 1.3.2. However I think, it's important to note at least from the aspect of Plasma Desktop, Dolphin still won't access and it's still saying "protocol died unexpectedly". I am having the same issue as well, but only on Neon, freshly ran updates today. Issue is nonexistant on Kubuntu 18.10 with backports on Plasma 5.14.2. > kdeconnect-cli --list-devices- lge: d3693ee0e6b125ba (paired and reachable) 1 device found > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/d3693ee0e6b125ba/sftp isMounted true > qdbus org.kde.kdeconnect /modules/kdeconnect/devices/d3693ee0e6b125ba/sftp mountAndWait true I am able to browse the phone successfully by inputting the directory manually. After upgrading to kdeconnect 1.3.2 same results for me. I can also browse the phone folders by pasting /run/user/... to Dolphin, but not by opening the phone object . lali@neonusr:~$ kdeconnect-cli --list-devices - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) lali@neonusr:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted true lali@neonusr:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait true lali@neonusr:~$ qdbus org.kde.kdeconnect /modules/kdeconnect/devices/104bfb976bc224ee/sftp getDirectories /run/user/1000/104bfb976bc224ee/storage/extSdCard: SD card /run/user/1000/104bfb976bc224ee/storage/extSdCard/DCIM/Camera: Camera pictures(SD card) /run/user/1000/104bfb976bc224ee/storage/sdcard0: Internal storage /run/user/1000/104bfb976bc224ee/storage/sdcard0/DCIM/Camera: Camera pictures(Internal storage) tmpfs 307364 12 307352 1% /run/user/1000 kdeconnect@192.168.0.103:/ 1048576000 0 1048576000 0% /run/user/1000/104bfb976bc224ee I also confirm to experience this on Neon 5.14.X , info details as wrote earlier. There is no update to the KDEconnect Android app and my phone runs an older Android (4.x). It would be nice to get a feedback from the develeopers if they can reproduce it or not. (In reply to Laosom from comment #33) > After upgrading to kdeconnect 1.3.2 same results for me. Can you elaborate on this? It was working with an older version of kdeconnnect, but upgrading to 1.3.2 caused problems? Can you downgrade and verify? > <quote chopped> > > I also confirm to experience this on Neon 5.14.X , info details as wrote > earlier. There is no update to the KDEconnect Android app and my phone runs > an older Android (4.x). > It would be nice to get a feedback from the develeopers if they can > reproduce it or not. I do not have problems on Fedora 28/29 Plasma 5.12.6/5.13.5. So no, I cannot reproduce this. None of us run Neon, as far as I am aware. I have not yet had time to install a Neon VM and test there. (In reply to Simon from comment #34) > I do not have problems on Fedora 28/29 Plasma 5.12.6/5.13.5. So no, I cannot > reproduce this. None of us run Neon, as far as I am aware. I have not yet > had time to install a Neon VM and test there. Hello Simon, No matter the kdeconnect version, it started to fail only on Neon from the 5.14.X updates. No issues on Arch or Kubuntu with Plasma 5.12 / 5.13 /5.14. What do you mean "none of us" ? You mean kdeconnect developers :))) ? Thanks. (In reply to Laosom from comment #35) > (In reply to Simon from comment #34) > > I do not have problems on Fedora 28/29 Plasma 5.12.6/5.13.5. So no, I cannot > > reproduce this. None of us run Neon, as far as I am aware. I have not yet > > had time to install a Neon VM and test there. > > Hello Simon, > > No matter the kdeconnect version, it started to fail only on Neon from the > 5.14.X updates. No issues on Arch or Kubuntu with Plasma 5.12 / 5.13 /5.14. Neon 5.14 seems to be the common denominator here, which unfortunately comes with a huge number of variables, so it will not be easy to chase down unless someone takes serious ownership of it > What do you mean "none of us" ? You mean kdeconnect developers :))) ? > Thanks. Yes, I mean none of the KDE Connect developers (In reply to Simon from comment #36) > (In reply to Laosom from comment #35) > > (In reply to Simon from comment #34) > > > I do not have problems on Fedora 28/29 Plasma 5.12.6/5.13.5. So no, I cannot > > > reproduce this. None of us run Neon, as far as I am aware. I have not yet > > > had time to install a Neon VM and test there. > > > > Hello Simon, > > > > No matter the kdeconnect version, it started to fail only on Neon from the > > 5.14.X updates. No issues on Arch or Kubuntu with Plasma 5.12 / 5.13 /5.14. > Neon 5.14 seems to be the common denominator here, which unfortunately comes > with a huge number of variables, so it will not be easy to chase down unless > someone takes serious ownership of it > > > What do you mean "none of us" ? You mean kdeconnect developers :))) ? > > Thanks. > Yes, I mean none of the KDE Connect developers Neon being the "techdemo" distro of KDE Plasma 5, and thought kdeconnect is integral part of it , it's strange to hear that and not a good promotion of Plasma . I hope someone will pick this up sooner or later. If I compare it with Kubuntu 18.10 with backports ppa the OS base is definitely older (Ubuntu 18.04 LTS) in NEON. I am going to check the other parts. > Yes, I mean none of the KDE Connect developers
I don't want to overreact anything and redundantly spiel however if not a single KDE developer got KDE neon related to Kdeconnect then wow, that's disgraceful indeed.
Same here with Google Nexus 6P running stock Android 8.1 and KDE Neon 5.14 with KDE Plasma 5.14.2 (In reply to Andras from comment #38) > > Yes, I mean none of the KDE Connect developers > I don't want to overreact anything and redundantly spiel however if not a > single KDE developer got KDE neon related to Kdeconnect then wow, that's > disgraceful indeed. I don't think I quite see the point being made here. KDE Connect has a very small development team (depending on how you count, somewhere between 5 and 10, probably closer to 5). I would rather use the system I am most familiar with (dnf/yum/RedHat) and be able to focus more effort on work and hobbies. This does not detract from the usefulness or value of Neon, just that its goals do not align with mine. (In reply to Laosom from comment #37) > Neon being the "techdemo" distro of KDE Plasma 5, and thought kdeconnect is > integral part of it , it's strange to hear that and not a good promotion of > Plasma . I hope someone will pick this up sooner or later. If I compare it > with Kubuntu 18.10 with backports ppa the OS base is definitely older > (Ubuntu 18.04 LTS) in NEON. I am going to check the other parts. One of KDE Connect's goals is to be distribution- and desktop-environment- independent, so I wouldn't describe it as being "integral" to Plasma 5 or Plasma 5 being integral to KDE Connect, even though we do integrate nicely with Plasma. (In reply to Simon from comment #40) Then It's a great example then users shouldn't rely on and cling to specific open source projects by names and shouldn't be loyal and shouldn't expect loyalty. I see some development makes its testing on more popular Distributions however as a not developer I assumed KDE project testing on KDE neon first as a matter of respect and if KDE neon itself wants to reach any level of popularity. If KDE Connect project is based on popularity so much then it should and I think it'll change its name sooner or later. Simon don't get me wrong, keep up the good work. Maybe I'll change my aspects and get other options that's all. (In reply to Simon from comment #40) > (In reply to Andras from comment #38) > > > Yes, I mean none of the KDE Connect developers > > I don't want to overreact anything and redundantly spiel however if not a > > single KDE developer got KDE neon related to Kdeconnect then wow, that's > > disgraceful indeed. > I don't think I quite see the point being made here. KDE Connect has a very > small development team (depending on how you count, somewhere between 5 and > 10, probably closer to 5). I would rather use the system I am most familiar > with (dnf/yum/RedHat) and be able to focus more effort on work and hobbies. > This does not detract from the usefulness or value of Neon, just that its > goals do not align with mine. > > (In reply to Laosom from comment #37) > > Neon being the "techdemo" distro of KDE Plasma 5, and thought kdeconnect is > > integral part of it , it's strange to hear that and not a good promotion of > > Plasma . I hope someone will pick this up sooner or later. If I compare it > > with Kubuntu 18.10 with backports ppa the OS base is definitely older > > (Ubuntu 18.04 LTS) in NEON. I am going to check the other parts. > One of KDE Connect's goals is to be distribution- and desktop-environment- > independent, so I wouldn't describe it as being "integral" to Plasma 5 or > Plasma 5 being integral to KDE Connect, even though we do integrate nicely > with Plasma. Thanks Simon for the explanation. I really thought Kdeconnect is a Plasma application an part of Plasma. The name of the product was the cause I think. I respect your great work with this great app. I don't use Neon as my daily driver either, as the KDE team states it's not quite a distro . They needed a stable base (Ubuntu LTS) for the latest KDE software to be built on. The first minor versions of a new release is always full of bugs , but the last builds were OK and very fine for daily use. The current version 5.14 is expecting 3 more bugfix releases in the upcoming months and compared to Kubuntu I can use more up-to-date KDE Software. For example Debian Stretch has Plasma 5.8.9 ; Kubuntu 18.04 LTS has Plasma 5.12.6 LTS ; Kubuntu 18.10 has Plasma 5.13.5 and with backports enabled 5.14.2 , but the KDE Applications is still older (18.04) compared to NEON (18.08.2). The interesting thing is Arch / Manjaro is also on the latest of everything and this bug does not exist there. Nathan Graham stated the following in his blog regarding 5.14 : https://pointieststick.wordpress.com/2018/10/14/this-week-in-usability-productivity-part-40/ "We apologize for these bugs and we’re working to get them fixed quickly! One of the reasons why bugs like this squeak through is that we don’t have enough pre-release QA testers. You could be one of them, and next week, your name could be in this list! Just check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!" It would be really nice if one you could test Neon VM and get in contact with the Neon team what's going on ;) Many thanks. (In reply to Laosom from comment #33) > After upgrading to kdeconnect 1.3.2 same results for me. > I can also browse the phone folders by pasting /run/user/... to Dolphin, > but not by opening the phone object . > > lali@neonusr:~$ kdeconnect-cli --list-devices > - Samsung GT-S7710: 104bfb976bc224ee (paired and reachable) > > lali@neonusr:~$ qdbus org.kde.kdeconnect > /modules/kdeconnect/devices/104bfb976bc224ee/sftp isMounted > true > > lali@neonusr:~$ qdbus org.kde.kdeconnect > /modules/kdeconnect/devices/104bfb976bc224ee/sftp mountAndWait > true > lali@neonusr:~$ qdbus org.kde.kdeconnect > /modules/kdeconnect/devices/104bfb976bc224ee/sftp getDirectories > /run/user/1000/104bfb976bc224ee/storage/extSdCard: SD card > /run/user/1000/104bfb976bc224ee/storage/extSdCard/DCIM/Camera: Camera > pictures(SD card) > /run/user/1000/104bfb976bc224ee/storage/sdcard0: Internal storage > /run/user/1000/104bfb976bc224ee/storage/sdcard0/DCIM/Camera: Camera > pictures(Internal storage) > > tmpfs 307364 12 307352 1% /run/user/1000 > kdeconnect@192.168.0.103:/ 1048576000 0 1048576000 0% > /run/user/1000/104bfb976bc224ee > > I also confirm to experience this on Neon 5.14.X , info details as wrote > earlier. There is no update to the KDEconnect Android app and my phone runs > an older Android (4.x). > It would be nice to get a feedback from the develeopers if they can > reproduce it or not. The same for me with Android 7.0, Neon 5.14.2, kdeconnect 1.3.2. I am neither able to browse the phone from /run/user/... neither in a terminal (I receive a permission error) nor in Dolphin (where the error is that the protocol kdeconnect died) I made a several attempts and increasing max_user_watches at boot seems to be the most significant one. Although I'm not sure if this single step would help for some so let me know how is it work: https://github.com/guard/guard/issues/229 http://blog.sorah.jp/2012/01/24/inotify-limitation https://askubuntu.com/questions/154255/how-can-i-tell-if-i-am-out-of-inotify-watches In short place this line into your /etc/sysctl.conf : fs.inotify.max_user_watches=100000 Also even if it helps, I don't think this is the real solution, I see it as a workaround only. Here is my diagnosis after a few hours with a Neon 5.14 VM: - The issue described is reproducible on a fresh installation - The issue described is not present on a build of the 1.3.2 branch on my Fedora system - The issue is not 100% reproducible. Sometimes I could click on the phone shortcut in Dolphin and everything would just work as normal. I could not figure out how to reliably trigger this good state, but it would seem to work for several tries after starting to work, then eventually give up - This happens with KDE Connect installed from a build from the master branch in git as well as installed from packages - This happens with package version 1.3.0-0ubuntu1 as well as the latest available 1.3.2-0xneon+18.04+bionic+build7 - The behavior for `kioclient cat kdeconnect://<device id>` differs between my Neon VM and my main Fedora system: - When kdeconnectd is not connected, on Fedora kioclient5 immediately exits with a 0 return code. On Neon, it pauses for ~2 seconds then exits with "The process for the kdeconnect://<device id> protocol died unexpectedly" and a non-zero code (specifically, 1) - When kdeconnectd is connected, the behavior is apparently the same (nothing successful-looking is ever written to the console) Most interestingly, nothing gets logged by kdeconnectd when the icon gets clicked in Neon. As in, no crash, nor failed connection. In Fedora, "stuff" happens (indicating the device is mounted, etc.) This suggests that something in the pipeline between KIO and KDE Connect is the cause of the trouble. After playing around with a KDE Neon VM I noticed the following error in ~/.xsession-errors: kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' QCoreApplication::arguments: Please instantiate the QApplication object first QCoreApplication::applicationDirPath: Please instantiate the QApplication object first QCoreApplication::applicationFilePath: Please instantiate the QApplication object first QCoreApplication::arguments: Please instantiate the QApplication object first KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = path = pid = 2439 KCrash: Arguments: kdeinit5: PID 2439 terminated. That got me looking at other KIO slaves (eg ftp) and apparently things have changed a bit: Instead of a .properties file they now use a .json file to define the plugins metadata and embed that using a dummy class having Q_PLUGIN_METADATA(IID "xxx" FILE "xxx.json") Then in the kdemain function they initialize a QCoreApplication object. Last but not least I now had to move kio_kdeconnect.so to /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/ Let me do some more test to see if it also works on my fedora system and I'll upload the patch to phabricator Simon & Erik Thanks for the updates and your efforts so far. This morning I have received an update for the KDE Connect app on my phone. Now I have the version 1.10 on the phone, and version 1.3.2 on my PC. In the changelog on the phone, one of the items is: "Fixed remote file browsing (needs desktop version 1.3.2!)" But, I still have the issue. No way to browse the phone files with Dolphin. (In reply to VosaXalo from comment #48) Yes, I saw it too and installed it with hope. I bet it was fix for remove file browsing maybe for many distribution even for OS from Rendmond but not for KDE neon. I just started to thinking about buying a new Windows licence if it gets more support even from Linux open sources. I tested the patch.. didn't seem to help unfortunately
$ ./kdeconnectd
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
Icon theme "gnome" not found.
kdeconnect.core: Broadcasting identity packet
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: It is a new device "Nexus6P"
kdeconnect.core: device "Nexus6P" not paired, ignoring packet "kdeconnect.battery"
kdeconnect.core: creating pairing handler for "6745be67c0caf8bb"
kdeconnect.core: device "Nexus6P" not paired, ignoring packet "kdeconnect.mpris.request"
kdeconnect.core: device "Nexus6P" not paired, ignoring packet "kdeconnect.runcommand.request"
kdeconnect.core: device "Nexus6P" not paired, ignoring packet "kdeconnect.notification"
kdeconnect.core: device "Nexus6P" not paired, ignoring packet "kdeconnect.notification"
kdeconnect.core: device "Nexus6P" not paired, ignoring packet "kdeconnect.notification"
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: It is a known device "Nexus6P"
kdeconnect.core: Sending onNetworkChange to 1 LinkProviders
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: LanLinkProvider newConnection
kdeconnect.core: LanLinkProvider newConnection
kdeconnect.core: LanLinkProvider received reply: "{\"id\":1541453857669,\"type\":\"kdeconnect.identity\",\"body\":{\"deviceId\":\"6745be67c0caf8bb\",\"deviceName\":\"Nexus6P\",\"protocolVersion\":7,\"deviceType\":\"phone\",\"incomingCapabilities\":[\"kdeconnect.sms.request_conversations\",\"kdeconnect.telephony.request_mute\",\"kdeconnect.telephony.request\",\"kdeconnect.mpris\",\"kdeconnect.notification\",\"kdeconnect.sms.request_conversation\",\"kdeconnect.findmyphone.request\",\"kdeconnect.ping\",\"kdeconnect.systemvolume\",\"kdeconnect.notification.reply\",\"kdeconnect.share.request\",\"kdeconnect.sftp.request\",\"kdeconnect.notification.request\",\"kdeconnect.mousepad.request\",\"kdeconnect.contacts.request_vcards_by_uid\",\"kdeconnect.sms.request\",\"kdeconnect.runcommand\",\"kdeconnect.battery.request\",\"kdeconnect.clipboard\",\"kdeconnect.contacts.request_all_uids_timestamps\"],\"outgoingCapabilities\":[\"kdeconnect.sms.messages\",\"kdeconnect.telephony\",\"kdeconnect.notification\",\"kdeconnect.contacts.response_uids_timestamps\",\"kdeconnect.findmyphone.request\",\"kdeconnect.ping\",\"kdeconnect.mousepad.keyboardstate\",\"kdeconnect.share.request\",\"kdeconnect.contacts.response_vcards\",\"kdeconnect.notification.request\",\"kdeconnect.mousepad.echo\",\"kdeconnect.mousepad.request\",\"kdeconnect.sftp\",\"kdeconnect.runcommand.request\",\"kdeconnect.mpris.request\",\"kdeconnect.systemvolume.request\",\"kdeconnect.battery\",\"kdeconnect.clipboard\"]}}\n"
kdeconnect.core: Starting client ssl (but I'm the server TCP socket)
kdeconnect.core: Socket successfully established an SSL connection
kdeconnect.core: It is a known device "Nexus6P"
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: It is a known device "Nexus6P"
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: It is a known device "Nexus6P"
kdeconnect.core: Pair answer
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "Nexus6P"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeconnect.plugin.contacts: sendRequest: Sending "kdeconnect.contacts.request_all_uids_timestamps" true
kdeconnect.plugin.contacts: Contacts constructor for device "Nexus6P"
kdeconnect.plugin.contacts: handleResponseVCards: Got 0 VCards
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: It is a known device "Nexus6P"
kdeconnect.plugin.sftp: Mount device: "Nexus6P"
kdeconnect.plugin.sftp: Created mounter
kdeconnect.plugin.sftp: Starting loop to wait for mount
kdeconnect.plugin.sftp: Unmount QObject(0x0)
kdeconnect.core: Converting IPv6 QHostAddress("::ffff:192.168.1.90") to IPv4 QHostAddress("192.168.1.90")
kdeconnect.plugin.sftp: Starting process: "sshfs kdeconnect@192.168.1.90:/ /run/user/1000/6745be67c0caf8bb -p 1739 -s -f -F /dev/null -o IdentityFile=/home/adam/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=+ssh-dss -o uid=1000 -o gid=1000 -o reconnect -o ServerAliveInterval=30 -o password_stdin"
QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in parameter list: NetworkPacket
kdeconnect.plugin.sftp: Process started
kdeconnect.plugin.sftp: "Nexus6P" "Remote filesystem mounted at /run/user/1000/6745be67c0caf8bb"
kdeconnect.plugin.sftp: stdout: "Warning: Permanently added '[192.168.1.90]:1739' (RSA) to the list of known hosts.\r\n"
kdeconnect.plugin.sftp: stdout: "Password authentication\r\n"
kf5.kio.widgets: KRun(0x5599a316b410) ERROR 143 "The process for the kdeconnect://6745be67c0caf8bb protocol died unexpectedly."
Wait... it worked after a reboot! Thank you! https://i.imgur.com/ZgtC5ef.png (In reply to NiO from comment #50) Nice, I'm glad it seems to be solved, thanks for the hard work! I noticed something tough and I hope not but if this issue remains somehow then may I highlight these two line from result above?: --- kdeconnect.plugin.sftp: Starting process: "sshfs kdeconnect@192.168.1.90:/ /run/user/1000/6745be67c0caf8bb -p 1739 -s -f -F /dev/null -o IdentityFile=/home/adam/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=+ssh-dss -o uid=1000 -o gid=1000 -o reconnect -o ServerAliveInterval=30 -o password_stdin" -- kdeconnect.plugin.sftp: stdout: "Warning: Permanently added '[192.168.1.90]:1739' (RSA) to the list of known hosts.\r\n" --- Technically speaking I know nothing about networking in deep but isn't KDEConnect asks for ssh-dss type algorithm and by the end the system try to give ssh-rsa? I mean is it possible it's something with cryptographic algorithms compatibility that the system in KDE neon won't provide the legacy one? Related to this, once I got this line for example: --- kdeconnect.plugin.sftp: stdout: "Unable to negotiate with 192.168.0.0 port 1739: no matching host key type found. Their offer: ssh-rsa\r\n" --- It's a long shot and maybe I'm speaking about nonsense but just in case I ask. You guys are awesome how fast the upgrades appeared in packages, thanks. I assume it was related to this bug also. I try to solve this on two desktop pc with two phone(beta app on both). I hope it's only for me and the main issue is solved. I still can't get Kdeconnect to work. My process was: Upgrade was done well, I mean everything installed flawlessly, kdevplatform52-libs was removed. Restart --> still won't work Remove /var/tmp/kdecache-user /~.cache/kio /~.config/kdeconnect and remove data from kdeconnect app on phone Restart --> still won't work The issue is the same, I mean I get the very same messages except right after the upgrade I got some additional stuff implemented by you guys I think, such as: kdeconnect.plugin.sftp: add to dolphin I'd like to note also, I still get the same result I mentioned above: kdeconnect.plugin.sftp: stdout: "Unable to negotiate with 192.168.0.0 port 1739: no matching host key type found. Their offer: ssh-rsa\r\n" Thank you for the fast patches! ...Unfortunately I still get the same error on my system. Deleted ~/config/kdeconnect (but couldn't find the other folders mentioned by Andras). Operating System: KDE neon 5.14 KDE Plasma-version: 5.14.2 Qt-version: 5.11.2 KDE Frameworks-version: 5.51.0 Kerne-version: 4.15.0-38-generic OS-type: 64-bit Processorer: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz Hukommelse: 15,6 GiB af RAM Please let me know if I can do anything to help your efforts (In reply to DozyDolphin from comment #54) > Thank you for the fast patches! > ...Unfortunately I still get the same error on my system. > Deleted ~/config/kdeconnect (but couldn't find the other folders mentioned > by Andras). > > Operating System: KDE neon 5.14 > KDE Plasma-version: 5.14.2 > Qt-version: 5.11.2 > KDE Frameworks-version: 5.51.0 > Kerne-version: 4.15.0-38-generic > OS-type: 64-bit > Processorer: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz > Hukommelse: 15,6 GiB af RAM > > Please let me know if I can do anything to help your efforts Sorry if this is overly obvious, but did you reboot after building and installing? I had to reboot to get my system / KIO to pick up the new change. Is your cmake configured for the correct install prefix? I upgraded all components, but getting same error even after reboot Git commit 560e8638e8ddc06a92f207fb21d5e8741ec608b7 by Albert Vaca, on behalf of Erik Duisters. Committed on 06/11/2018 at 13:20. Pushed by albertvaka into branch 'master'. A QApplication object needs to be instantiated for kio-kdeconnect to work on KDE Neon Summary: kio-kdeconnect fails to start on KDE Neon because it does not instantiate a QApplication object Test Plan: Install on a KDE Neon 5.14 system or VM Pair an android phone Browse the phone's filesystem using dolphin Reviewers: #kde_connect, #frameworks, albertvaka Reviewed By: #kde_connect, albertvaka Subscribers: sredman, apol, jriddell, nicolasfella, albertvaka, kdeconnect Tags: #kde_connect Differential Revision: https://phabricator.kde.org/D16692 M +3 -2 kio/CMakeLists.txt A +26 -0 kio/kdeconnect.json D +0 -16 kio/kdeconnect.protocol M +12 -0 kio/kiokdeconnect.cpp https://commits.kde.org/kdeconnect-kde/560e8638e8ddc06a92f207fb21d5e8741ec608b7 Git commit 8388ed0603f0d04d7adde2152b077dbd29275ee3 by Albert Vaca, on behalf of Erik Duisters. Committed on 06/11/2018 at 13:22. Pushed by albertvaka into branch '1.3'. A QApplication object needs to be instantiated for kio-kdeconnect to work on KDE Neon Summary: kio-kdeconnect fails to start on KDE Neon because it does not instantiate a QApplication object Test Plan: Install on a KDE Neon 5.14 system or VM Pair an android phone Browse the phone's filesystem using dolphin Reviewers: #kde_connect, #frameworks, albertvaka Reviewed By: #kde_connect, albertvaka Subscribers: sredman, apol, jriddell, nicolasfella, albertvaka, kdeconnect Tags: #kde_connect Differential Revision: https://phabricator.kde.org/D16692 M +3 -2 kio/CMakeLists.txt A +26 -0 kio/kdeconnect.json D +0 -16 kio/kdeconnect.protocol M +12 -0 kio/kiokdeconnect.cpp https://commits.kde.org/kdeconnect-kde/8388ed0603f0d04d7adde2152b077dbd29275ee3 I have also upgraded my kdeconnect package to kdeconnect:amd64 (1.3.2-0xneon+18.04+bionic+build7, 1.3.2-0xneon+18.04+bionic+build8) and also the kdeconnect app to 1.10. Cleaned up /home/.../.config/kdeconnect folder, reboot Phone readded . Same error during filebrowse in Dolphin :( Since I seem to be the only one this patch seemed to have helped, I thought I should mention I also built and installed the latest sshfs and libfuse3 from source at the suggestion of another user. I don't personally understand the low level interactions between these packages and KDE Connect so I don't know if this is relevant at all, or if it will help anyone, but KDE Neon packages a very outdated version of sshfs from 2016. Default package versions: $ sshfs --version SSHFS version 2.8 FUSE library version: 2.9.7 fusermount version: 2.9.7 using FUSE kernel interface version 7.19 My current version: $ sshfs --version SSHFS version 3.5.0 FUSE library version 3.1.1 using FUSE kernel interface version 7.26 fusermount3 version: 3.1.1 Do this at your own risk, it may have other implications on your system. There might be a reason KDE Neon chose to provide old versions of these packages. The only issue I'm currently having is I lose pairing after every reboot and have to re-pair my device every time I need to access it. I've done so much mucking around with system components I may have screwed that up myself though. (In reply to Laosom from comment #59) > I have also upgraded my kdeconnect package to > > kdeconnect:amd64 (1.3.2-0xneon+18.04+bionic+build7, > 1.3.2-0xneon+18.04+bionic+build8) > > and also the kdeconnect app to 1.10. > Cleaned up /home/.../.config/kdeconnect folder, reboot > Phone readded . > Same error during filebrowse in Dolphin :( Version 1.3.2-0xneon+18.04+bionic+build8 doesn't have these patches. Patch added 2018-11-06 at 13:22:50 Package created 2018-11-05 at 22:54 Compile package from sources. You should get 1.3.3 soon, which fixes the issue. (In reply to Simon from comment #55) > (In reply to DozyDolphin from comment #54) > > Thank you for the fast patches! > > ...Unfortunately I still get the same error on my system. > > Deleted ~/config/kdeconnect (but couldn't find the other folders mentioned > > by Andras). > > > > Operating System: KDE neon 5.14 > > KDE Plasma-version: 5.14.2 > > Qt-version: 5.11.2 > > KDE Frameworks-version: 5.51.0 > > Kerne-version: 4.15.0-38-generic > > OS-type: 64-bit > > Processorer: 4 × Intel® Core™ i7-7567U CPU @ 3.50GHz > > Hukommelse: 15,6 GiB af RAM > > > > Please let me know if I can do anything to help your efforts > > Sorry if this is overly obvious, but did you reboot after building and > installing? I had to reboot to get my system / KIO to pick up the new > change. Is your cmake configured for the correct install prefix? No need to apologize... I did reboot, but didn't build anything. I got an update for KdeConnect on my system, so I figured that was the one that fixed it - my bad. I'll wait it out. Ok, although it's closed I'd note, I think it's because the older 1.3 version of KDE Connect what KDE neon kept asks for dated ssh-dss type of cryptographic algorithm what is disabled by default on current OpenSSH.
It's highly NOT recommended but you can enable it by placing a line into /etc/ssh/ssh_conf. However you should make a copy previously:
sudo cp /etc/ssh/ssh_config /etc/ssh/ssh_config.factory-defaults
Then add the following to ssh_config file:
PubkeyAcceptedKeyTypes +ssh-dss
Even if you can't wait and make this modification, you should undo it right after you got KDE Connect 1.4.
Correct me If I I'm wrong.
(correction for comment #64) I wanted to write "you should undo it right after you got KDE Connect 1.3.3" what allegedly fix this issue. First of all, I apologize for all my rude replies. Nevertheless I'd like to give a feedback, 1.3.3 version of KDE Connect just arrived on my two pc with KDE neon and it works awesome with my cellphones. Thank you so much guys, many thanks for all your hard work! I can confirm too, that with version 1.3.3 of KDEConnect the issue is finally gone. Thank you very much for the support, and the work done. Everything works for me after update, thanks for a great work This was working when I compiled the patched version, but I'm getting a new error from kdeconnectd now When trying to pair desktop to phone: I get request on my phone and I accept, the KDE Connect gui refreshes and it just says (not paired) When trying to pair phone to desktop: I get an accept/reject dialog, I accept. The following error occurs on kdeconnectd terminal output In both cases, the phone completely fails to pair now. Any ideas? kdeconnect.core: KdeConnect daemon starting kdeconnect.core: onStart kdeconnect.core: KdeConnect daemon started Icon theme "gnome" not found. kdeconnect.core: Broadcasting identity packet kdeconnect.core: Starting client ssl (but I'm the server TCP socket) kdeconnect.core: Socket succesfully stablished an SSL connection kdeconnect.core: It is a new device "Nexus6P" 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 "Nexus6P" kdeconnect.core: creating pairing handler for "6745be67c0caf8bb" kdeconnect.core: Pair request kdeconnect.plugin.sftp: add to dolphin kdeconnect.plugin.sftp: Created device: "Nexus6P" ./kdeconnectd: symbol lookup error: /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_contacts.so: undefined symbol: _ZNK6Device2idEv If I disable the plugins one-by-one from the desktop GUI, every subsequent plugin fails So far it has happened with SMS plugin, Contacts plugin, now Find Device Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) ./kdeconnectd: symbol lookup error: /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_findthisdevice.so: undefined symbol: _ZNK6Device2idEv apt purge and reinstall all kdeconnect packages fixed the problem. Disregard Problem solved for me too with kdeconnect 1.3.3 Thanks a lot guys , awesome work. Best wishes. Problem solved also for me after installing kdeconnect 1.3.3 and rebooting system Thank you! Problem solved with the new kdeconnect version 1.3.3 in KDE Neon. Thanks guys! |
