https://bugs.kde.org/show_bug.cgi?id=3D355258 Maciej Stanczew changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com --- Comment #22 from Maciej Stanczew --- I experience a similar issue. I have three NFS mounts in fstab, with option "x-systemd.automount" set (so they should only be mounted when something tr= ies accessing corresponding directories). After system boot none of the three shares is mounted, but then when one is mounted on demand, plasmashell trig= gers the mount of other two shares: Jul 31 22:41:05 hostname systemd[1]: n-media.automount: Got automount reque= st for /n/media, triggered by 669 (mpd) Jul 31 22:41:05 hostname systemd[1]: Mounting /n/media... Jul 31 22:41:05 hostname systemd[1]: Mounted /n/media. Jul 31 22:41:05 hostname systemd[1]: n-pacman.automount: Got automount requ= est for /n/pacman, triggered by 518 (plasmashell) Jul 31 22:41:05 hostname systemd[1]: Mounting /n/pacman... Jul 31 22:41:05 hostname systemd[1]: Mounted /n/pacman. Jul 31 22:41:05 hostname systemd[1]: n-backup.automount: Got automount requ= est for /n/backup, triggered by 518 (plasmashell) Jul 31 22:41:05 hostname systemd[1]: Mounting /n/backup... Jul 31 22:41:05 hostname systemd[1]: Mounted /n/backup. As in original description, it's not possible to unmount any of the shares: Jul 31 22:44:14 hostname systemd[1]: Unmounting /n/backup... Jul 31 22:44:14 hostname systemd[1]: n-backup.automount: Got automount requ= est for /n/backup, triggered by 518 (plasmashell) Jul 31 22:44:14 hostname systemd[1]: Mounting /n/backup... Jul 31 22:44:15 hostname systemd[1]: Mounted /n/backup. This only happens with Device Notifier applet active -- without it, everyth= ing works correctly. The patch from comment #15 fixes both of above issues -- plasmashell no lon= ger triggers any unwanted mounts in those scenarios. Regarding simultaneous unmount (as described in comment #16): manually runn= ing umount with multiple targets always works (all shares are properly unmounte= d). It's only when doing this from systemd that sometimes shares are remounted = by plasmashell: # systemctl stop n-backup.mount n-media.mount n-pacman.mount Job for n-media.mount canceled. Jul 31 23:02:53 hostname systemd[1]: Unmounting /n/backup... Jul 31 23:02:53 hostname systemd[1]: Unmounting /n/media... Jul 31 23:02:53 hostname systemd[1]: Unmounting /n/pacman... Jul 31 23:02:53 hostname systemd[1]: n-media.automount: Got automount reque= st for /n/media, triggered by 508 (plasmashell) Jul 31 23:02:53 hostname systemd[1]: Unmounted /n/backup. Jul 31 23:02:53 hostname systemd[1]: Mounting /n/media... Jul 31 23:02:53 hostname systemd[1]: Unmounted /n/pacman. Jul 31 23:02:53 hostname systemd[1]: Mounted /n/media. Still, could the patch from comment #15 be merged regardless of this remain= ing issue? In my case the patch only improves the behavior, as it eliminates al= most all of unwanted mounts (leaving only a specific corner-case that is simultaneous unmounting). --=20 You are receiving this mail because: You are watching all bug changes.=