Thunar hangs on startup when unavailable network shares are in bookmarks

Submitted by Luca Steinke

Assigned to Xfce Bug Triage

Link to original bug (#12467)

Description

Apparently, when using x-systemd-automount, Thunar seems to somehow access the share and doesn't respond on startup. Journal shows:

-- Subject: Unit mnt-server-data.mount has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit mnt-server-data.mount has begun starting up. Feb 24 11:01:13 my-computer mount[1730]: Unable to find suitable address. Feb 24 11:01:13 my-computer systemd[1]: mnt-server-data.mount: Mount process exited, code=exited status=32 Feb 24 11:01:13 my-computer systemd[1]: Failed to mount /mnt/server/data. -- Subject: Unit mnt-server-data.mount has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

-- Unit mnt-server-data.mount has failed.

-- The result is failed.

steps to reproduce: /etc/fstab:

systemd automounts

//192.168.1.10/data /mnt/server/data cifs credentials=/etc/samba/credentials/server,noauto,x-systemd.automount,x-systemd.device-timeout=7 0 0 UUID=9A7C301A7C2FF025 /mnt/win10 ntfs-3g noauto,x-systemd.automount,remove_hiberfile 0 0

→ you don't need a real (samba) share, because it has to be not available for this bug to occur anyway. Seems to be related to #12265 – apparently for all network shares. Thunar doesn't respond after the timeout, too.

Version: 1.6.10