GNOME Bugzilla – Bug 322507
Stale Nautilus bookmarks lock gnome applications
Last modified: 2008-08-04 16:52:35 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: major Version: GNOME2.10.2 2.10.x Gnome-Distributor: Debian Synopsis: bookmark to "remote" host Bugzilla-Product: nautilus Bugzilla-Component: Bookmarks Bugzilla-Version: 2.10.x Description: Description of Problem: If you use autofs with nfs and add a bookmark for a directory on a remote system, nautilus hangs (about 10s - the timeout from autofs?) if you open a browser window or browse your bookmarks. ... Steps to reproduce the problem: 1. add a remote directory to your bookmarks (like "/nfs/anotherserver/home/" ) 2. open your browser window, while "anotherserver" is not running Actual Results: Nautilus hangs (completely) for about 20s. Expected Results: Nautilus shoudn't try to access bookmarks unless somebody wants to browse them. How often does this happen? Always (and also with nautilus 2.8.3 on another workstation) ------- Bug moved to this database by unknown@gnome.bugs 2005-11-26 17:34 UTC ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this. The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was ibf_c@web.de.
Similar to bug #154277 which is fixed. What version of nautilus do you use?
I'm using nautilus 2.8.3, 2.10.? and 2.12.2 - it's always the same problem. I think this is not the same Bug (it should be fixed in 2.12.2 already?). The problem is, that nautilus seems to acces all bookmarks on startup (at least if they're normal folders), but there is no difference between a normal "folder" and the way I access network shares (with autofs ...). - right? So it will hang until autofs gets a timeout. The timeout (in terminal) is about 5s if I try to "access" a not-running computer, but nautilus hangs longer. Is it necessary to access the bookmark always yout start nautilus, edit yout bookmarks, or just on the bookmark in the "bookmark-manager" (to delete or modify it)?
I recently added a ftp-server with login to my bookmarks in Nautilus. Filroller (debian unstable v.2.12.2) try to access this bookmerk when I open the Save-Dialog, I get several times the Dialog to enter my Password-Manager Password. I think the bookmarks should only be accessed when I click on them. That would solve many Problems. Or is there a reason for this behaviour.
I am experiencing very similar situation. I have a SSH entry in .gtk-bookmarks, which uses a "authorized_keys2" that requires authentication. Right click on gnome-panel, properties. Then the "Authentication Required" dialog shows up 3 times.
(In reply to comment #4) > I am experiencing very similar situation. > > I have a SSH entry in .gtk-bookmarks, which uses a "authorized_keys2" that > requires authentication. > > Right click on gnome-panel, properties. > Then the "Authentication Required" dialog shows up 3 times. > Versions info: Slackware 10.2 Gnome 2.14.1 (compiled by dropline gnome) gtk+-1.2.1 gtk+2-2.8.17 nautilus-2.14.1
Please fix this problem, because it affects many applications, and unexperienced users will never find the cause, causing lots of false reports, irritation and dissatisfaction with gnome. Several occasions which are caused by this bug: 1. Several applets cause strange system behaviour (for example, timer applet) 2. File-roller called from nautilus right click menu causes long locks: file-roller --default-dir=/home/user/Desktop/pub --add /home/user/Desktop/pub/somedir: if there are stale bookmarks on the system, this dialog loads after several minutes only, and it takes the same time to close if closed. 3. Unresponsive applications: for example sound-juicer takes long time to load similar to case 2. Think about users with laptops: if user moves between networks, some remote bookmars contantly get stale and users will experience annoing problems. Sometimes removing bug is a bad solution, since those bookmars in most cases would be useful again when back on their native network. Please also change the summary of the bug - current description is uninformative. I think, "Stale Nautilus bookmarks lock gnome applications" would be more correct Please, please, take a closer look into this problem. If you can not reproduce the bug yourselves, I can describe a 100% test case if it helps.
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/72607 "Nautilus trying to stat its bookmarks at startup makes bad interaction with nfs Binary package hint: nautilus I have a bookmark in nautilus to an NFS-mounted partition, if I log in in gnome, with autofs/NFS enabled, I cannot log in, nautilus blocks the entire login process by hanging on NFS because the server is unavailable. While it's true that the problem lies in the NFS architecture, I think that nautilus should not stat/test existence for its bookmarks - not sure how to handle the problem. In any case, I cannot login now even rebooting the system (of course I will disable NFS), a timeout to the existence test should be added. Attaching a backtrace in case it helps. (gdb) where
+ Trace 89272
I can confirm that this bug continues to exist in Nautilus 2.20.0 (GNOME 2.20.2 on OpenSolaris)
I'm duping this bug to 532911 because it contains a bug. *** This bug has been marked as a duplicate of 532911 ***