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.
CONFIRMATION: After reproducing the problem on recent "debian testing/forky", "kde neon dev" and new immutable "kde linux" distros, I can confirm that the bug (still) exists. RELATED BUGS: While searching for a cause / trigger of one of my own bugs reported to debian called "triggered by re-mounts using Systemd-Automount : Dolphin erroneously moves 1 level (../) up in all tabs and warns about 'current location changed'" (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109671) I stumbled across this one. When searching for dolphin and automount on bugs.kde.org (https://bugs.kde.org/buglist.cgi?quicksearch=dolphin%20automount) there are currently 30 entries. So it seems there is still ongoing work to make mounting and unmounting of devices more flawless when using Dolphin and other KDE parts. STEPS TO REPRODUCE: 1. create dirs for mount point(s) e.g. /tmp/docs (in case of an immuatble OS like "KDE linux") or /mnt/docs 2. add mount data to /etc/fstab : > //127.0.0.1/linuxdoc /mnt/docs cifs guest,noperm,noatime,nofail,x-systemd.automount,x-systemd.device-timeout=5s,x-systemd.mount-timeout=7s,x-systemd.idle-timeout=10s 0 0 3. systemctl daemon-reload 4. mount -a 5. make sure there is no tab open in dolphin with /tmp/docs, respectively /mnt/docs 6. umount -lf /tmp/docs OR umount -lf /mnt/docs 7. close and open dolphin again 8. systemctl start tmp-docs....automount 9. ctrl + click on the network share in remote part of places panel in dolphin to open in a new tab 10. switch to another tab that is not part of the users home dirs (e.g. switch to /usr/share instead) 11. observe the other tab title (without switching to it) changing OBSERVED RESULT: [debian testing / forky] dolphin : 25.04.3 (about dialog) / 4:25.04.3-1 (apt) kio-framework : 6.13.0-7 (apt) observations : - still occurs, on every automount timeout - happens also in the unselected tab with the network share, when another tab is selected / focussed - in the places panel under remote there is just 1 entry (unlike on kde plasma 6.5 dev - neon) for the share ["kde neon" dev edition with latest updates from 22.September 2025] dolphin : 25.11.70 (about dialog) / 4:25.08.1+p24.04+vunstable+git20250916.0903-0 (apt) kio-framework : 6.18.0+p24.04+vunstable+git20250915.0232-0 (apt) observations : - still occurs, on every automount timeout - happens also in the unselected tab with the network share, when another tab is selected / focussed - sometimes there are 2 entries in the places panel under remote for the same network share, one has an orange icon (probably to show that it's not mounted) the other has a green icon and is coming and going with the idle timeouts ["kde linux" - kde plasma 6.6 dev - with latest updates from 22.September 2025] dolphin : 25.11.70 (about dialog) / 25.08.1 (discover) kio-framework : ? (don't know how to get the version without an ordinary pkg manager) observations : - still occurs, on every automount timeout - happens also in the unselected tab with the network share, when another tab is selected / focussed - same behaviour like with debian testing (strange, had expected more like neon) - but setting up the scenario / mounts with immutable "kde linux" was harder (so created mount points (temporarly) in /tmp, while /mnt and /media are not existing and a lot is readonly)
Created attachment 185362 [details] Screenshot on new KDE LINUX regarding 'location changed' for automounted network share