After some testing I can confirm that my nautilus stalling issue is related to bookmarking NFS/autofs-mounted shares.
After manually removing those bookmarks from ~/.gtk-bookmarks, nautilus starts up immediately.
Doing some tests with "strace nautilus --no-desktop" reveals that nautilus issues numerous access()-calls to each bookmarked folder, yielding ENOENT for those NFS/autofs-shares after a timeout of some seconds for each call. Since nautilus does *lots* of those calls even before showing its initial window, startup takes endlessly in this case.
Interestingly, these access() calls appear only for the first instance of nautilus, any subsequently started nautilus instances already "know", that those folders are not available (probably via CORBA/orbit?), they don't even load ~/.gtk-bookmarks.
Manually removing bookmarked NFS/autofs folders from ~/.gtk-bookmarks solved that issue at least in my case.
This might be a different behaviour then.
After some testing I can confirm that my nautilus stalling issue is related to bookmarking NFS/autofs-mounted shares.
After manually removing those bookmarks from ~/.gtk-bookmarks, nautilus starts up immediately.
Doing some tests with "strace nautilus --no-desktop" reveals that nautilus issues numerous access()-calls to each bookmarked folder, yielding ENOENT for those NFS/autofs-shares after a timeout of some seconds for each call. Since nautilus does *lots* of those calls even before showing its initial window, startup takes endlessly in this case.
Interestingly, these access() calls appear only for the first instance of nautilus, any subsequently started nautilus instances already "know", that those folders are not available (probably via CORBA/orbit?), they don't even load ~/.gtk-bookmarks.
Manually removing bookmarked NFS/autofs folders from ~/.gtk-bookmarks solved that issue at least in my case.