Bug 127100 - Nautilus hangs or will not start if it has unavailable automount server in tree
Summary: Nautilus hangs or will not start if it has unavailable automount server in tree
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-01 21:19 UTC by Xander D Harkness
Modified: 2016-06-07 22:44 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-10-05 13:06:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Xander D Harkness 2004-07-01 21:19:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040626 Firefox/0.9.1

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
times out.

Version-Release number of selected component (if applicable):
nautilus-2.6.0-4

How reproducible:
Always

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.

Additional info:

Comment 1 Xander D Harkness 2004-07-04 21:53:56 UTC
I have subsequently tried twice to reproduce this and have failed on
both occasions.



Comment 2 Alexander Larsson 2004-10-05 13:06:11 UTC
There was another bug about /net that seems fixed too. Closing this.
Please reopen if you see this again.


Note You need to log in before you can comment on or make changes to this bug.