https://bugs.kde.org/show_bug.cgi?id=517343

            Bug ID: 517343
           Summary: dolphin keeps requesting systemd automount and failure
                    results in a 10s timeout for every operation
    Classification: Applications
           Product: dolphin
      Version First 25.08.2
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

I have a data partition that is mounted on demand by systemd when I want to
access it, but I also pass it through to my Windows virtual machine when it's
running - it then becomes unavailable to the host system. In fstab it looks
like this:

LABEL=windata      /mnt/windata    ntfs3  
defaults,user,nofail,x-systemd.automount,x-systemd.idle-timeout=5min  0 0

This used to work great in the past, but not anymore. Now when the VM is
running and the partition is not available to the host, dolphin takes 10
seconds to start, 10 seconds to open any folder, 10 seconds to display file
properties dialog, etc.

This is what shows up in the logs:

Mar 09 15:13:52 legion systemd[1379]: Started Dolphin - File Manager.
Mar 09 15:13:52 legion systemd[1]: mnt-windata.automount: Got automount request
for /mnt/windata, triggered by 6264 (dolphin)
Mar 09 15:13:52 legion systemd[1]: Expecting device
/dev/disk/by-label/windata...
Mar 09 15:14:02 legion systemd[1]: dev-disk-by\x2dlabel-windata.device: Job
dev-disk-by\x2dlabel-windata.device/start timed out.
Mar 09 15:14:02 legion systemd[1]: Timed out waiting for device
/dev/disk/by-label/windata.
Mar 09 15:14:02 legion systemd[1]: Dependency failed for /mnt/windata.
Mar 09 15:14:02 legion systemd[1]: mnt-windata.mount: Job
mnt-windata.mount/start failed with result 'dependency'.
Mar 09 15:14:02 legion systemd[1]: dev-disk-by\x2dlabel-windata.device: Job
dev-disk-by\x2dlabel-windata.device/start failed with result 'timeout'.

I'm not sure if this is a result of a change in dolphin, some kde famework or
maybe systemd changed it's behavior. It used to work fine like a month ago.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.6.2
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 40 GiB of RAM (34.9 GiB usable)
Graphics Processor: AMD Radeon 680M

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to