I have a question about kio-fuse, and didn’t find documentation to answer it.
With gnome-based desktops I was used to having user-space-driven filesystems mounted automatically by the desktop or manually through the file manager as a fuse mount under /run/user/[UID]/gvfs/…
which I needed e.g. to rsync the pictures from my mobile and my camera to the computer.
While I was under the impression that kio-fuse is supposed to do the very same task under /run/user/[UID]/kio-fuse/… , things mounted with Dolphin, such as cameras and mobiles (MTP) or webdav just don’t appear there (Kubuntu 25.10 and Kinoite 43).
Is this some bug or misconfiguration, or is it the normal state that kio-fuse does not mount these kio file systems?
As far as I found, kio-fuse should not need any direct user interaction and should be driven and notified solely over dbus. So I would have expected that what I do mount in Dolphin, would appear as a regular file system under /run/user/[UID]/kio-fuse.
Having stable and predictable paths for kio-fuse mounts is surely a welcome improvement, but unless I am misunderstanding this will not solve OP’s problem, that is: one needs to perform some action in order to trigger the kio-fuse mount.
Just accessing a device in Dolphin does not really mount it, as Dolphin relays on KIO. Only if from Dolphin I try to open a file or directory with a non-KDE app, then kio-fuse is triggered.
It seems we still lack a way to just mount a specific resource with kio-fuse from Dolphin. I am thinking something like “Mount” command in the context menu of a “Places” entry. Maybe a feature request could be filed on Bugzilla for this.
i’ve found it reliable to use KDE connect to browse folders on my mobile
even after reboots and disconnects, as long as i still have that tab open in dolphin, i can just reconnect with KDE connect and refresh the view in dolphin to get everything back.
however, it does not work that way when using the disks and devices “open in file manager” workflow…. then i have to use a new tab each time.