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

            Bug ID: 500413
           Summary: Dolphin Navigates Up One Level Each Time Automount
                    Times Out
    Classification: Applications
           Product: dolphin
           Version: 24.12.2
          Platform: Mageia RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-n...@kde.org
          Reporter: thomas.bi...@tmgo.net
                CC: kfm-de...@kde.org
  Target Milestone: ---

STEPS TO REPRODUCE:

1. Set up a CIFS systemd-automount share in /etc/fstab. The relevant line is:

> //server/name /mnt/name cifs 
> [...],noauto,x-systemd.automount,x-systemd.idle-timeout=30,x-systemd.mount-timeout=10
>  0 0

2. Open Dolphin and navigate to /mnt/name.
3. Leave the Dolphin window inactive for 30 seconds.

OBSERVED RESULT:

The unmount is triggered correctly, but Dolphin displays an error message:
> Current location changed, '/mnt/name' is no longer accessible.

Dolphin then navigates up one level to /mnt. If you are in a deeper directory
level, Dolphin will navigate up one level every 30 seconds until it reaches
/mnt.

EXPECTED RESULT:

Dolphin should handle the unmount gracefully without navigating up the
directory tree.

SOFTWARE/OS VERSIONS:

- Linux/KDE Plasma: Mageia 10 Cauldron (Wayland)
- KDE Plasma Version: 5.24.4
- KDE Frameworks Version: 6.10.0
- Qt Version: 6.8.1
- Build ABI: x86_64-little_endian-lp64
- Kernel: linux 6.6.77-desktop-1.mga10
- CIFS-utils: 7.1

ADDITIONAL INFORMATION:

In the logs, I can see the successive unmounts, and when Dolphin navigates up a
level, it requests the mount point again until it reaches /mnt.

> Feb 19 14:59:31 myhost.mydomain systemd[1]: mnt-name.automount: Got automount 
> request for /mnt/name, triggered by 516317 (dolphin)
> Feb 19 14:59:31 myhost.mydomain systemd[1]: Mounting mnt-name.mount...
> Feb 19 14:59:31 myhost.mydomain kernel: CIFS: enabling forceuid mount option 
> implicitly because uid= option is specified
> Feb 19 14:59:31 myhost.mydomain kernel: CIFS: enabling forcegid mount option 
> implicitly because gid= option is specified
> Feb 19 14:59:31 myhost.mydomain kernel: CIFS: Attempting to mount 
> //server/name
> Feb 19 14:59:31 myhost.mydomain systemd[1]: Mounted mnt-name.mount.
> Feb 19 15:00:12 myhost.mydomain systemd[1]: Unmounting mnt-name.mount...
> Feb 19 15:00:12 myhost.mydomain systemd[1]: mnt-name.mount: Deactivated 
> successfully.
> Feb 19 15:00:12 myhost.mydomain systemd[1]: Unmounted mnt-name.mount.
> Feb 19 15:00:13 myhost.mydomain systemd[1]: mnt-name.automount: Got automount 
> request for /mnt/name, triggered by 516317 (dolphin)
> Feb 19 15:00:13 myhost.mydomain systemd[1]: Mounting mnt-name.mount...
> Feb 19 15:00:13 myhost.mydomain kernel: CIFS: enabling forceuid mount option 
> implicitly because uid= option is specified
> Feb 19 15:00:13 myhost.mydomain kernel: CIFS: enabling forcegid mount option 
> implicitly because gid= option is specified
> Feb 19 15:00:13 myhost.mydomain kernel: CIFS: Attempting to mount 
> //server/name
> Feb 19 15:00:13 myhost.mydomain systemd[1]: Mounted mnt-name.mount.
> Feb 19 15:01:04 myhost.mydomain systemd[1]: Unmounting mnt-name.mount...
> Feb 19 15:01:04 myhost.mydomain systemd[1]: mnt-name.mount: Deactivated 
> successfully.
> Feb 19 15:01:04 myhost.mydomain systemd[1]: Unmounted mnt-name.mount.

RELATED BUGS:

This behavior contradicts the expected behavior described in bug #453796, which
indicates that the CIFS share should be automatically unmounted after the
desired timeout while Dolphin is still active.

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

Reply via email to