https://bugs.kde.org/show_bug.cgi?id=516179
Bug ID: 516179
Summary: systemd automounted FUSE mounts cause KIO to think the
current directory is unavailable when it still is
Classification: Frameworks and Libraries
Product: frameworks-kio
Version First 6.22.0
Reported In:
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
SUMMARY
When attempting to access a systemd automounted FUSE mount triggered by KIO via
Dolphin, approximately 5 seconds after the mount becomes live KIO will generate
an item deleted notification for the current path that ultimately causes
Dolphin to print a warning stating "Current location changed, XYZ is no longer
available." and kick the current directory up exactly one level (and only one
level, given that the path is obviously still accessible).
STEPS TO REPRODUCE
1. Configure a systemd mount and automount unit for any filesystem mounted
through FUSE. In my particular setup, I'm using a custom mount helper that
automounts a restic backup repository, but I've seen the same behavior using
the fuse.borgfs helper from Borg Backup as well.
2. Attempt to access the automount path through Dolphin. KIO will trigger the
automount, Dolphin will pause until the mount goes live (on FUSE filesystems
like Restic and Borg, there's often a multi-second delay before the actual
mount completes), then the icons will populate once the FS is readable.
3. Wait approximately (almost exactly?) 5 seconds. Dolphin will emit a warning
about the current location being inaccessible and kick the URL bar up one
level.
OBSERVED RESULT
It doesn't matter how "deep" you manage to dive into the FUSE filesystem before
the timeout occurs, Dolphin will always emit the exact same warning and boot
you up exactly one level (even if the new level still belongs to the same FUSE
mount, which more or less verifies that the mount is indeed still accessible).
EXPECTED RESULT
Nothing should happen and Dolphin should not kick the current directory up one
level.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
ADDITIONAL INFORMATION
This doesn't occur with kernel mounted filesystems such as CIFS (since I also
use those on the same system and they work just fine). Inserting arbitrary
delays into the mount helper scripts to ensure the FUSE filesystem stabilizes
before Dolphin populates the view with the FS contents doesn't seem to help-
delaying it by 5, 10, 15, 30 seconds... doesn't matter, and Dolphin will always
kick up one level about 5 seconds after the mount goes live. No error messages
are present in journalctl when this happens.
--
You are receiving this mail because:
You are watching all bug changes.
