GNOME Bugzilla – Bug 163579
after login nautilus does not start anymore
Last modified: 2005-01-20 12:42:28 UTC
Please describe the problem: I tried to connect to a smb share on a windows pc which hang forever in the connection dialog and also stalled any other nautilus operations, e.g. clicking on desktop icons... After several retries with killing nautilus and restarting I gave up on connecting to the smb share and logged out. The log out of gnome also hang forever and I therefore killed it with ctrl-alt-bkspc. After a new log in nautilus did not come up again :-( Steps to reproduce: I don't knoe if the problem can be reproduced because since then I never could start nautilus again. Eventually the following will lead to the problem 1. Connect to a non existent smb share 2. Wait until nautilus hangs forever 3. Kill nautilus in the command line 4. Repeat steps 1-3 until nautlius no longer starts Actual results: Nautilus just hangs therefore it is unusable, e.g. no icons and gnome save as dialogs also hang forever. Expected results: Normal nautilus startup. Does this happen every time? Yes Other information: nautilus -c hangs forever after printing: running nautilus_self_check_search_uri running nautilus_self_check_file_utilities running nautilus_self_check_file_operations running nautilus_self_check_directory and the last few lines of an strace of the hanging nautilus shows: [...] rt_sigsuspend([] <unfinished ...> --- SIGRTMIN (Unknown signal 32) @ 0 (0) --- <... rt_sigsuspend resumed> ) = -1 EINTR (Interrupted system call) sigreturn() = ? (mask now [RTMIN]) rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], Cool = 0 rt_sigsuspend([] <unfinished ...> Running bonobo-slay did not solve it.
I could debug it further and found out that the problem is a call to gnome_vfs_get_volume_monitor(); and following there I found out that this call hangs forever: the_volume_monitor = g_object_new (GNOME_VFS_TYPE_VOLUME_MONITOR_CLIENT, NULL); Any idea why??
*** This bug has been marked as a duplicate of 161997 ***