SUMMARY Since yesterday I can no longer browse files on my device (Samsung S6 Active) STEPS TO REPRODUCE 1. Browse Device via KDE Connect plasmoid 2. Folder opens with two sub-folders, "All files" and "Camera pictures" 3. Clicking on either folder results in a "does not exist" message OBSERVED RESULT The file or folder /run/user/1001/6a2c2a9ed051c297/storage/emulated/0/DCIM/Camera does not exist. Accessing /run/user/1001/6a2c2a9ed051c297/ in a terminal shows it as empty. I have tried rebooting both the computer and the device, deleting config files, unpairing and pairing the device to no avail. I can ping the computer and the device from the computer. I can send files from the device to the computer. I can use the device as a remote and to control Amarok, etc. I have all functions except I cannot browse for files since yesterday. EXPECTED RESULT I should be able to browse folders and files on the device as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.51.0 KDE Frameworks Version: 5.13.5 Qt Version: 5.11.1 ADDITIONAL INFORMATION Kernel Version: 4.18.17-200.fc28.x86_64 OS Type 64-bit
I looked at the permissions for fusermount and realize that the stickybit was not set - so: chmod rwsr-xr-x /usr/bin/fusermount I still cannot browse the device: The file or folder /run/user/1001/6a2c2a9ed051c297/storage/emulated/0/DCIM/Camera does not exist. I get this errors in the system log: kdeconnectd[2135]: QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in parameter list: NetworkPacket and in .xsessions: /usr/bin/fusermount: entry for /run/user/1001/6a2c2a9ed051c297 not found in /etc/mtab and in mtab: tmpfs /run/user/1001 tmpfs rw,nosuid,nodev,relatime,size=1638348k,mode=700,uid=1001,gid=1001 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
> and in .xsessions: That should be .xsession-errors
related: bug 400935
also related: Bug 400945 Bug 400780 Bug 400703
Solved: According to ntoan96 ( bug 400703 ) "The newest version of kdeconnect on Android is 1.10 which only works fine with kdeconnect 1.3.2 or later. Meanwhile, the kdeconnect package on Kubuntu is at version 1.3.1. So you have to either donwgrade the Android app or upgrade the PC package." Installing kde-connect-1.3.3-1.fc28 from Koji and rebooting resolved the problem for me The files, which are currently in testing, can be downloaded here (fedora users) https://koji.fedoraproject.org/koji/buildinfo?buildID=1163017