On a bootc-based laptop (based on Silverblue 44), I have a enabled automount unit of a NFS folder (to /var/mnt/public) . The mount point is a nautilus bookmark.
When the mount fails (when NFS server is not reachable), this seems to be affecting Nautilus, and often (~50% of time) double-clicking to open a file (not on the NFS ofc) doesn’t work. When it fails, I can see these logs on journalctl (here we can see I try to open a text file)
juin 03 18:55:54 systemd[3827]: Started dbus-:1.2-org.gnome.TextEditor@64.service.
juin 03 18:55:55 systemd[3827]: Started app-flatpak-org.gnome.TextEditor-713717750.scope.
juin 03 18:55:55 mount[37799]: mount.nfs: Failed to resolve server filer: Name or service not known
juin 03 18:55:55 systemd[1]: var-mnt-public.mount: Mount process exited, code=exited, status=32/n/a
juin 03 18:55:55 systemd[1]: var-mnt-public.mount: Failed with result 'exit-code'.
juin 03 18:55:55 systemd[1]: Failed to mount var-mnt-public.mount - Otera Public NFS share mount.
juin 03 18:55:55 flatpak[37816]: bwrap: Can't bind mount /oldroot/var on /newroot/var: Unable to apply mount flags: remount "/newroot/var/mnt/public": No such device
juin 03 18:55:55 systemd[1]: var-mnt-public.automount: Got automount request for /var/mnt/public, triggered by 15969 (gvfsd-recent)
juin 03 18:55:55 flatpak[37809]: error: Failed to sync with dbus proxy
juin 03 18:55:55 systemd[1]: Mounting var-mnt-public.mount - Otera Public NFS share mount...
juin 03 18:55:55 systemd[3827]: dbus-:1.2-org.gnome.TextEditor@64.service: Main process exited, code=exited, status=1/FAILURE
juin 03 18:55:55 systemd[3827]: dbus-:1.2-org.gnome.TextEditor@64.service: Failed with result 'exit-code'.