Red Hat Bugzilla – Bug 127100
Nautilus hangs or will not start if it has unavailable automount server in tree
Last modified: 2016-06-07 18:44:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
I added a /net automount point using File -> Connect to server ->
enter URL - so I stuck in /net/fileserver
Now I am at a different location if I start Nautilus it takes over two
minutes to start in browse mode. If I just start a single window then
is is much faster. If I have a window open and I launch Nautilus in
browse mode all other windows become unusable, until the /net share
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start amd automounter
2.use file -> connect to server and enter url
3.make the server unavailable and start nautilus
Actual Results: Nautilus will hang for a period of a couple of
minutes until it realises that the share in not available and it
causes all other Nautilus windows to freeze.
Expected Results: Nautilus should recognise that the share is not
available as fast as showmount -e fileserver does and return.
Problems with one window should not impact the use of other windows.
I have subsequently tried twice to reproduce this and have failed on
There was another bug about /net that seems fixed too. Closing this.
Please reopen if you see this again.