SUMMARY STEPS TO REPRODUCE 1. Pair device 2. Enable file permissions on Android device 3. Try to browse file system from Dolphin OBSERVED RESULT "Error when accessing filesystem. sshfs finished with exit code 1" EXPECTED RESULT Browsing the filesystem on my phone. SOFTWARE/OS VERSIONS Android: Oreo Linux/KDE Plasma: Fedora 32 plasmashell 5.18.3 Qt: 5.13.2 KDE Frameworks: 5.68.0 kf5-config: 1.0 ADDITIONAL INFORMATION I can see the folders I enabled on the kdeconnect android app but when I try to browse them I get the aforementioned error.
Running into the same issue Device paired and all other functions are working as expected. File permissions are in place on Android, mapping to both the root directory of the phone and the root directory of the SD card. When attempting to read from either location via Dolphin I get "Error when accessing filesystem. sshfs finished with exit code 1." Was previously working until 9/8/2020 Software/OS Android: Honeycomb (10) Linux: Manjaro 20.0.3 (KDE) DE: Plasma 9.15.9 Qt: 5.15.0-5 KDE Framework: 5.73.0-1
Confirmed on 22.12.0
I see the same behaviour on my Fedora 37 with kde-connect 22.12.1-1.fc37 trying to connect to Android 12.1 with KDE Connect 1.21.1 from F-Droid. In journalctl I see the following line that seems relevant: Jan 21 15:26:09 hal9000 kdeconnectd[2038]: QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in parameter list: NetworkPacket
(In reply to Joel Busch from comment #3) > I see the same behaviour on my Fedora 37 with kde-connect 22.12.1-1.fc37 > trying to connect to Android 12.1 with KDE Connect 1.21.1 from F-Droid. > > In journalctl I see the following line that seems relevant: > > Jan 21 15:26:09 hal9000 kdeconnectd[2038]: QDBusAbstractAdaptor: Cannot > relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input > type in parameter list: NetworkPacket I am also seeing the same problem today using the latest version of KDE Connect 1.21.1 (just updated as it occurred with the previous version) and kdeconnectd 22.12.1-1.fc37 . I have Android 12 One UI version 4.1 on my Samsung S10+
Discovered that if the desktop kdeconnect widget is made sticky, so that the window stays open, one can drag and drop files from the desktop and they will be deposited in the default Download folder on the phone. The error occurs when one attempts to browse the folders on the phone using the kdeconnect desktop widget.
Could this be related to https://bugs.kde.org/show_bug.cgi?id=443155 ?
(In reply to Marek from comment #6) > Could this be related to https://bugs.kde.org/show_bug.cgi?id=443155 ? No - that pertains to files sent from the phone to the desktop - whereas I have no problem doing that with the current versions of KDEConnect and openssh. The bug reported here is about an inability to browse folders on the phone. As soon as "Browse this device" is selected in the KDEConnect desktop widget a stream of error windows with an audio alarm occurs until the widget is closed. Current openssh version is 8.8p1-7.fc37
(In reply to SP from comment #7) This is the same behaviour as here still in version 22.12.3 Dropping files on the widget is nice, temporary, workaround - thanks.
This affects me also. KDEconnect version: 22.12.3-0ubuntu1~ubuntu22.10~ppa1 Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Quadro M1200/PCIe/SSE2 Manufacturer: Dell Inc. Product Name: Precision 5520
I forgot to add: KDEconnect version 1.22.2 from F-Droid on a Oneplus 8T running LineageOS for Microg (LOS20/Android 13).
I have this problem too after update to 22.12.3. For now I have timeshift snapshot with 22.12.1 - it works for me. I have to update system manually - all packages are up to date Neon and only Connect have to be 22.12.1 to do it's magic. On android side it's Samsung S9 Android 10, F-droid and GooglePlay versions have same behaviour after clean install and all permissions checked for app. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.19 Kernel Version: 5.19.0-1022-lowlatency (64-bit) Graphics Platform: Wayland
It works as expected in kdeconnect 22.12.3 (on ubuntu 23.04, KDE 5.104)
Is anyone working on this? It's been quite some time that this bug exist. Thank you!!
For the record I haven't had this error in a while. Currently on plasmashell 5.27.1 Qt: 5.15.8 KDE Frameworks: 5.103.0 kf5-config: 1.0 KDE Connect 1.22.1 (Android)
Created attachment 158352 [details] screenshot I'm still facing this bug. kdeconnect 23.04.0-1 KDE Connect 1.24.1 app (installed on Android 6) Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Graphics Platform: Wayland
(In reply to Patrick Silva from comment #15) > Created attachment 158352 [details] > screenshot > > I'm still facing this bug. > > kdeconnect 23.04.0-1 > KDE Connect 1.24.1 app (installed on Android 6) > Operating System: Arch Linux > KDE Plasma Version: 5.27.4 > KDE Frameworks Version: 5.105.0 > Qt Version: 5.15.9 > Graphics Platform: Wayland Nevermind. sshfs package was not installed on my system. Installed it right now and kde connect works as expected.
(In reply to Justin from comment #9) > This affects me also. > KDEconnect version: 22.12.3-0ubuntu1~ubuntu22.10~ppa1 > > Operating System: Kubuntu 22.10 > KDE Plasma Version: 5.27.3 > KDE Frameworks Version: 5.104.0 > Qt Version: 5.15.6 > Kernel Version: 5.19.0-38-generic (64-bit) > Graphics Platform: X11 > Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz > Memory: 31.2 GiB of RAM > Graphics Processor: Quadro M1200/PCIe/SSE2 > Manufacturer: Dell Inc. > Product Name: Precision 5520 I just updated to Kubuntu 23.04 and this still affects me. My desktop also has this bug.
(In reply to whoopsdecade from comment #14) > For the record I haven't had this error in a while. Currently on > plasmashell 5.27.1 > Qt: 5.15.8 > KDE Frameworks: 5.103.0 > kf5-config: 1.0 > KDE Connect 1.22.1 (Android) Forgot to add: Android 10
I can confirm that the bug appears to have been resolved. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.9 Kernel Version: 6.2.11-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland kdeconnectd 22.12.3-1.fc27 kdeconnect 1.22.1 Android 12 One UI 4.1
Upgraded to KDE Connect 1.24.3 on my S10+ (see specs of my OS etc above). Tried to browse folders on the phone and could no longer access. Rebooted computer - problem persists. Restarted phone - problem resolved.
Yes, after recent F-Droid upgrade of KDEConnect I can confirm it is working again! Thanks devs!
I don't know why it was not working before, but on my system the problem is in sshfs now. Until version 3.7.3 (https://github.com/libfuse/sshfs/commit/c2715f74537a4487934ae22d3c0edf9c7fb779aa) it does not recognize a parameter PubkeyAcceptedKeyTypes, which is used to overwrite the defaults of "OpenSSH 8.8p1" (https://bugs.kde.org/show_bug.cgi?id=443155) ---- Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-41-generic (64-bit) Graphics Platform: X11 SSHFS version 3.7.1 FUSE library version 3.10.5 using FUSE kernel interface version 7.31 fusermount3 version: 3.10.5 OpenSSH_8.9p1 Ubuntu-3ubuntu0.1, OpenSSL 3.0.2 15 Mar 2022 ----
Could this be related to the issue #1610 that GSConnect users are experiencing ( https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/1610 )? When trying to mount with newer KDEConnect clients the message "This location could not be displayed." pops up because it is trying to mount the root path instead of a path that KDEConnect has permissions to (i.e. /storage/emulated/0 )
This error still persist on KDE Neon (which is odd considering that it it a kde app) ``` Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.1510 Kernel Version: 6.2.0-32-generic (64-bit) Graphics Platform: X11 SSHFS version 3.7.1 FUSE library version 3.10.5 fusermount3 version: 3.10.5 Android KDE Connest: 1.27.1 ```
This error still persists on KDE Neon 6 SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.5.0-21-generic (64-bit)
Is this issue being worked on? It's been years, and it's still an issue. KDE Neon 6 with KDE Connect 1.30.1 on a Galaxy S24+, but his has been an issue for me for years with three different phones and multiple version of KDE Connect and KDE. Yes, I have sshfs installed, and no KDE Connect will not allow me to browse files on my phone. This is not a "NOR Crash" importance, it's a broken application that doesn't work importance.
Hitting this too. I've found that in my case, the fuse kernel module was not loaded. After modporbing manually, I was able to open the primary storage but sdcard stayed locked. I went to settings on the phone, removing and re-adding the sdcard, which instead of fixing this broke everything, now I can't browse neither the primary storage. "exit code 1" isn't very useful to debug what is the problem (the same error when the module was missing, the same now when I really don't know what is wrong if it worked for a tiny while with the same software versions and setup ...) Pretty please with sugar on top, can we get at least the full error message and not just the exit code?
I can confirm the error. When I try to call a paired device with Dolphin, I get the return value 1 from sshfs, but no connection. KDE-Neon Plasma 6.1.1 Framework 6.3.0 QT 6.7.0 Kernel 6.5.0-41-generic X11 Intel Core i5-4460 16 GB Ram nvidia/msi NV117
I've been using KDE Connect quite happily for years but suddenly it is now producing this error. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-113-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 27.3 GiB of RAM Graphics Processor: RENOIR Samsung Galaxy A20e Android 11
Just discovered that I can 'push' a file from the smartphone to the PC. It seem it's the 'pull' that's the issue.
I confirm the bug. Now I got the same error.
I get the same error, however I added my phone as an host in `.ssh/config`: >Host <Phone Name> > HostName <IP Address> > Port 1739 > PubkeyAcceptedKeyTypes +ssh-rsa > IdentityFile ~/.config/kdeconnect/privateKey.pem and then manually mount: > sshfs Pixel8Pro:/ /run/user/1000/<Device ID>/ The error toast still pops-up constantly but I am able to navigate files until a timeout Android: 14 Linux: EndeavourOS Plasma: 6.1.2 Qt: 6.2.7 KDE Frameworks: 6.3.0 Kernel: 6.9.7-arch1-1 Graphics Platform: Wayland OpenSSH: 9.8p1-1 sshfs: 3.7.3-1 KDEConnect (Linux): 25.05.2-1 KDEConnect (Android): 1.31.1 Tested on 2 PC/Phone connections
Also encountering this issue after an update. It looks like the sshfs command is failing with the following error message... fuse: unknown option(s): `-o ssh-rsa' If I modify plugins/sftp/mounter.cpp and delete the "HostKeyAlgorithms=+ssh-dss\\,ssh-rsa" line then it works again. Maybe sshfs or fuse changed how they parse options and is now getting confused by the comma? But it's not entirely clear to me why this option is even necessary. It is for compatibility with older systems or something?
I'm also having the same issue after an update. Tried what lionucs suggested, but it doesn't work for me. > $ sshfs -odebug,sshfs_debug,loglevel=debug -o rw,nosuid,nodev,identityfile=/home/user/.config/kdeconnect/privateKey.pem,port=1739 -oHostKeyAlgorithms=+ssh-rsa kdeconnect@ip-address:/ /run/user/1000/device-id > SSHFS version 3.7.3 > executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-ologlevel=debug> <-oidentityfile=/home/user/.config/kdeconnect/privateKey.pem> <-oport=1739> <-oHostKeyAlgorithms=+ssh-rsa> <-2> <kdeconnect@ip-address> <-s> <sftp> > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf > debug1: Connecting to ip-address [ip-address] port 1739. > debug1: Connection established. > debug1: identity file /home/user/.config/kdeconnect/privateKey.pem type -1 > debug1: identity file /home/user/.config/kdeconnect/privateKey.pem-cert type -1 > debug1: Local version string SSH-2.0-OpenSSH_9.8 > debug1: Remote protocol version 2.0, remote software version SSHD-CORE-0.14.0 > debug1: compat_banner: no match: SSHD-CORE-0.14.0 > debug1: Authenticating to ip-address:1739 as 'kdeconnect' > debug1: load_hostkeys: fopen /home/user/.ssh/known_hosts2: No such file or directory > debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory > debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: algorithm: ecdh-sha2-nistp256 > debug1: kex: host key algorithm: ssh-rsa > debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none > debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug1: SSH2_MSG_KEX_ECDH_REPLY received > debug1: Server host key: ssh-rsa SHA256:y6BdBO0md6YzWuNHNbstu5akZ2WC/oNxLBxzKfYBEr4 > debug1: load_hostkeys: fopen /home/user/.ssh/known_hosts2: No such file or directory > debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory > debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory > debug1: Host '[ip-address]:1739' is known and matches the RSA host key. > debug1: Found key in /home/user/.ssh/known_hosts:7 > debug1: rekey out after 4294967296 blocks > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug1: SSH2_MSG_NEWKEYS received > debug1: rekey in after 4294967296 blocks > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug1: Authentications that can continue: password,keyboard-interactive,publickey > debug1: Next authentication method: publickey > debug1: Will attempt key: /home/user/.config/kdeconnect/privateKey.pem explicit > debug1: Trying private key: /home/user/.config/kdeconnect/privateKey.pem > sign_and_send_pubkey: no mutual signature supported > debug1: Next authentication method: keyboard-interactive > Password authentication > (kdeconnect@ip-address) Password: I don't know what password to use there. Android: 7 Linux: EndeavourOS Plasma: 6.1.2 Qt: 6.7.2 KDE Frameworks: 6.3.0 Kernel: 6.9.8 Graphics Platform: Wayland OpenSSH: 9.8p1 sshfs: 3.7.3 KDEConnect (Linux): 24.05.2 KDEConnect (Android): 1.30.1
Adding PubkeyAcceptedKeyTypes=+ssh-rsa makes the command work. > $ sshfs -odebug,sshfs_debug,loglevel=debug -o rw,nosuid,nodev,identityfile=/home/user/.config/kdeconnect/privateKey.pem,port=1739 -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedKeyTypes=+ssh-rsa kdeconnect@ip-address:/ /run/user/1000/device-id But when accessed from Dolphin, I still get the error and the folders in my device appear empty. However, if I don't use Dolphin but copy files using the terminal, it works. That's good enough for me, but it'd be great if Dolphin can be made to work as it used to. Another bit of information that may be helpful is that I tried downgrading kdeconnect and the linux kernel with the headers and none brought this functionality back.
In case it helps. I am still able to access my SMS messages from my PC.
I appear to be having the same issue on Arch. Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.8-zen1-1-zen (64-bit) Graphics Platform: Wayland openssh version: 9.8p1-1 sshfs version: 3.7.3-2 After I saw no useful information in the journal, I decided to strace kdeconnectd to see what commands it executes and try running them myself in a terminal for more information. I found this command: > sshfs kdeconnect@<device ip>:/ /run/user/1000/<random guid> -p <port> -s -f -F /dev/null "-o" "IdentityFile=/home/mini_bomba/.config/kdeconnect/privateKey.pem" "-o" "StrictHostKeyChecking=no" "-o" "UserKnownHostsFile=/dev/null" "-o" "HostKeyAlgorithms=+ssh-dss\\,ssh-rsa" "-o" "PubkeyAcceptedKeyTypes=+ssh-rsa" "-o" "uid=1000" "-o" "gid=1000" "-o" "reconnect" "-o" "ServerAliveInterval=30" "-o" "password_stdin" Running that command in a terminal (with a modified, existing mountpoint path) resulted in the following output: > command-line line 0: Bad key types '+ssh-dss,ssh-rsa'. > read: Connection reset by peer As I did not recognize the ssh-dss key type, I removed it from the options and tried running the command again, which resulted in the phone's file system being successfully mounted. I confirmed that the ssh-dss key type was the issue by removing the other key type (ssh-rsa) instead, which resulted in a similar "Bad key types" error. Based on this investigation I suspect that support for the ssh-dss key type must've been removed or disabled in a recent ssh version, but doesn't appear critical to the function of kdeconnect - it just needs to stop explicitly requesting it.
Maybe it helps to see a solution on Kubuntu 24.04 from a parallel thread: The "debuild" hint for sshfs from here (https://bugs.kde.org/show_bug.cgi?id=477673#c11) together with an upgrade of kdeconnect app was the solution on my Kubuntu 24.04. Haven't checked whether that version of sshfs might be in backports repo to avoid building it. ii kdeconnect 23.08.5-0ubuntu5 amd64 connect smartphones to your desktop devices ii sshfs 3.7.3-1.1build3 amd64 filesystem client based on SSH File Transfer Protocol I had to install version 1.31 of the app from f-droid, in playstore it is still on 1.30
It may be helpful to have a look at these two workarounds. I haven't tried the solution myself as it's only a mild inconvenience to me to use a data cable to transfer files for a little bit. https://www.reddit.com/r/kde/comments/1ck6vp9/bypass_kdeconnect_sshfs_errors/
*** Bug 479954 has been marked as a duplicate of this bug. ***
*** Bug 489511 has been marked as a duplicate of this bug. ***
*** Bug 491248 has been marked as a duplicate of this bug. ***
sshfs is failing with this message: > command-line line 0: Bad key types '+ssh-dss,ssh-rsa'. sshfs is being called with these arguments: > sshfs kdeconnect@IPADDRESSHERE:/ /tmp/1000-runtime-dir.grt/SOMEUUIDHERE -p SOMEPORTNUMBER -s -f -F /dev/null -o IdentityFile=/home/USERNAME/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=+ssh-dss\,ssh-rsa -o PubkeyAcceptedKeyTypes=+ssh-rsa -o uid=1000 -o gid=1000 -o reconnect -o ServerAliveInterval=30 -o password_stdin One of the older workaround scripts I saw added some more commandline arguments, but this didn't help me. Instead I had to remove (or replace) the mention of "ssh-dss" in the commandline. I wrote this shim and put it in my $PATH: ``` #!/bin/sh exec /usr/bin/sshfs $(echo "$@" | sed 's|ssh-dss|ssh-rsa|g') ``` Kdeconnect mounts now work again. It's probably fine to permanently nueter mentions of ssh-dss, however, I still recommend removing this script when the bug is fixed because it doesn't safely quote things and this might cause problems if spaces ever get introduced into the commandline arguments.
I've just had an update to the mobile app. It now works. Thanks to whoever fixed it.
Still have this bug. Using Debian Trixie (Kernel: 6.10.6-amd64) with: SSHFS version 3.7.3 FUSE library version 3.14.0 using FUSE kernel interface version 7.31 fusermount3 version: 3.14.0 It worked before on Debian Bookworm (dont know sshfs version there), but in Bookworm virtual keyboard doesnt work and some other things with it. I have version 1.32 KDE Connect on my Pixel 6 which is running Android 15 Beta (AP41.240726.009) and version 23.08.5 KDE Connect on pc. How bug works for me: when pressing 'Browse this device' on my pc i get 'Error when accessing filesystem. sshfs finished with exit code 1'
(In reply to Hales from comment #43) > sshfs is failing with this message: > > > command-line line 0: Bad key types '+ssh-dss,ssh-rsa'. > > sshfs is being called with these arguments: > > > sshfs kdeconnect@IPADDRESSHERE:/ /tmp/1000-runtime-dir.grt/SOMEUUIDHERE -p SOMEPORTNUMBER -s -f -F /dev/null -o IdentityFile=/home/USERNAME/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=+ssh-dss\,ssh-rsa -o PubkeyAcceptedKeyTypes=+ssh-rsa -o uid=1000 -o gid=1000 -o reconnect -o ServerAliveInterval=30 -o password_stdin > > One of the older workaround scripts I saw added some more commandline > arguments, but this didn't help me. Instead I had to remove (or replace) > the mention of "ssh-dss" in the commandline. I wrote this shim and put it > in my $PATH: > > ``` > #!/bin/sh > exec /usr/bin/sshfs $(echo "$@" | sed 's|ssh-dss|ssh-rsa|g') > ``` > > Kdeconnect mounts now work again. It's probably fine to permanently nueter > mentions of ssh-dss, however, I still recommend removing this script when > the bug is fixed because it doesn't safely quote things and this might cause > problems if spaces ever get introduced into the commandline arguments. Tried this and it worked. i made some minor changes, instead of putting the script to $PATH, i renamed /usr/bin/sshfs to /usr/bin/sshfs-original and made a new script file /usr/bin/sshfs with the script: #!/bin/sh exec /usr/bin/sshfs_original $(echo "$@" | sed 's|ssh-dss|ssh-rsa|g')
> Tried this and it worked. i made some minor changes, instead of putting the > script to $PATH, i renamed /usr/bin/sshfs to /usr/bin/sshfs-original and > made a new script file /usr/bin/sshfs with the script: > #!/bin/sh > exec /usr/bin/sshfs_original $(echo "$@" | sed 's|ssh-dss|ssh-rsa|g') Browsing it is slow as hell tho
How can this bug still exist after 4 year escapes me...
(In reply to Paschalis from comment #48) > How can this bug still exist after 4 year escapes me... KDE connect is an awesome app but unfortunately its reliability varies depending on your phone model and/or Android version etc. I've seen this when changing phones, it just doesn't behave the same way on some (worse), great on others. Doesn't seem like any particular Android setting or permission affects this.. it's something to do with the way the app works. Must be hard to support such a wide range of functionality across Android versions but it's still annoying when it doesn't work as expected. I moved on to sharing files via Syncthing dropboxes, it's probably not faster but way more reliable. Unfortunately no a similar alternative for sharing urls 😥
Wasn't working during summer on e/OS Murena phone, but it is now working, possibly due to multiple factors in various updates. I am not technical so can't pin point. On 27/10/2024 15:53, whoopsdecade wrote: > https://bugs.kde.org/show_bug.cgi?id=419897 > > --- Comment #49 from whoopsdecade <jcdopsec@gmail.com> --- > (In reply to Paschalis from comment #48) >> How can this bug still exist after 4 year escapes me... > KDE connect is an awesome app but unfortunately its reliability varies > depending on your phone model and/or Android version etc. I've seen this when > changing phones, it just doesn't behave the same way on some (worse), great on > others. Doesn't seem like any particular Android setting or permission affects > this.. it's something to do with the way the app works. Must be hard to support > such a wide range of functionality across Android versions but it's still > annoying when it doesn't work as expected. I moved on to sharing files via > Syncthing dropboxes, it's probably not faster but way more reliable. > Unfortunately no a similar alternative for sharing urls 😥 >
(In reply to Jaz-z from comment #50) > Wasn't working during summer on e/OS Murena phone, but it is now > working, possibly due to multiple factors in various updates. I am not > technical so can't pin point. That's part of the problem. It's not constant, varies from phone to phone. Which points to larger issues honestly but doesn't make debugging these easier.
(In reply to whoopsdecade from comment #51) > (In reply to Jaz-z from comment #50) > > Wasn't working during summer on e/OS Murena phone, but it is now > > working, possibly due to multiple factors in various updates. I am not > > technical so can't pin point. > > That's part of the problem. It's not constant, varies from phone to phone. > Which points to larger issues honestly but doesn't make debugging these > easier. It not only varies from phone to phone, it's different computers as well. Both my laptop and desktop have Neon 24.04, both updated from 22.04. My laptop has no issues connecting but I can't brows my phone from my desktop, and haven't been able to for quite some time now. I've pretty much given up on it now, I don't think they'll ever fix it. It's really too bad, KDEConnect was such a great program, it's a real shame.