I had to kill nautilus and now it hangs when I restart it. This is probably this bug: http://bugzilla.gnome.org/show_bug.cgi?id=161997 A fix is to compile gnome-vfs without hal support or to compile gnome-vfs with hal support but without the additional gentoo patch gnome-vfs-2.8.3-updated_hal_support.patch. So something must be wrong with that patch or it at least triggers the bug. Reproducible: Sometimes Steps to Reproduce: 1. kill nautilus several times until nautilus hangs 2. 3. Actual Results: nautilus hangs Expected Results: run and e.g. show icons on desktop Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r2 i686) ================================================================= System uname: 2.6.10-gentoo-r2 i686 AMD Athlon(tm) XP 2800+ Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1,sys-kernel/linux26-headers-2.6.8 .1-r2 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3 /env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /us r/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ ftp://ftp.easynet.nl/mirror /gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X acpi alsa apache2 apm arts avi berkdb bitmap-fonts bluetooth cdr cr ypt cups dvd eds encode esd f77 faad fam flac font-server foomaticdb fortran gdb m gif gimpprint gnome gpm gstreamer gtk gtk2 hal imagemagick imlib ipv6 irmc jav a jpeg junit kde libg++ libwww mad matroska mikmod motif mozilla mpeg ncurses nl s oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline sam ba sdl slang spell sqlite sse ssl svga tcltk tcpd tiff truetype truetype-fonts t ype1-fonts wxwindows x86 xml xml2 xmms xosd xprint xv xvid zlib"
there's probably something not quite right with the patch, or with hal. But your report lacks any useful info on what actually is going wrong. If you want to help, you should try to help out on the upstream bugreport. Since not a lot of ppl experience your problem (you are the first to report while it's been stable for quite a while), it's probably something on your machine thats troublesome.
Hi! I hoped you would not close the bug so fast. I know the description is vague but if you ask me what else I should provide I will do. starting nautilus in gdb and ctrl-c when it hangs produces these three backtraces for the 3 threads: Thread 1: (gdb) bt #0 0x40e10af3 in __pthread_sigsuspend () from /lib/libpthread.so.0 #1 0x40e1061b in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #2 0x40e0d018 in pthread_cond_wait@GLIBC_2.0 () from /lib/libpthread.so.0 #3 0x40d885a6 in link_wait () from /usr/lib/libORBit-2.so.0 Thread 2: (gdb) bt #0 0x41079a11 in fts_children () from /lib/libc.so.6 #1 0x41079aca in poll () from /lib/libc.so.6 #2 0x40e0dcce in __pthread_manager () from /lib/libpthread.so.0 #3 0x40e0df07 in __pthread_manager_event () from /lib/libpthread.so.0 #4 0x41082e6a in clone () from /lib/libc.so.6 Thread 3: Program received signal SIGINT, Interrupt. [Switching to Thread 16386 (LWP 31849)] 0x41079a11 in fts_children () from /lib/libc.so.6 (gdb) bt #0 0x41079a11 in fts_children () from /lib/libc.so.6 #1 0x41079aca in poll () from /lib/libc.so.6 #2 0x40e7e04c in g_main_loop_get_context () from /usr/lib/libglib-2.0.so.0 #3 0x0818e2b8 in ?? () #4 0x00000007 in ?? () #5 0xffffffff in ?? () #6 0x40e7ce16 in g_main_context_query () from /usr/lib/libglib-2.0.so.0 #7 0x00000007 in ?? () #8 0x00000009 in ?? () #9 0x0818e2b8 in ?? () #10 0x40e7d4f6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #11 0x0817c698 in ?? () #12 0xffffffff in ?? () #13 0x7fffffff in ?? () #14 0x0818e2b8 in ?? () #15 0x00000007 in ?? () Looks normal to me. When I add printfs to the various pieces, nautilus, gnome-vfs etc I can trace the problematic call to be: In the function: nautilus_self_check_directory the first call to nautilus_directory_file_monitor_add (directory, &data_dummy, TRUE, TRUE, 0, NULL, NULL); calls filemonitor_add calls vfs_file_monitor_add calls nautilus_directory_monitor_add_internal (directory, NULL, client, monitor_hidden_files, monitor_backup_files, file_attributes, callback, callback_data); calls nautilus_monitor_directory (directory->details->uri); calls monitor_add_internal (uri, TRUE); calls path_is_on_readonly_volume calls gnome_vfs_get_volume_monitor(); Last call does not return but hangs forever. So the real bug seems to be that gnome_vfs_get_volume_monitor does not return. Any ideas why?? As I already pointed out http://bugzilla.gnome.org/show_bug.cgi?id=161997 this bug seems to be the same. So my question would be what lock could prevent gnome-vfs from working and how to debug it. Thanks, Fabian
There is now a fix in gnome-vfs. http://bugzilla.gnome.org/show_bug.cgi?id=161997 Unfortunately I couldn't reproduce the bug again but it is very likely that the upstream fix solved the problem. thanks a lot, Fabian
Upstream patch is here: http://bugzilla.gnome.org/attachment.cgi?id=36164&action=view although I'm not sure whether we need to apply it or not.
*** Bug 80666 has been marked as a duplicate of this bug. ***
