gnome-panel / nautilus hang due to gnome-vfs-daemon

This is probably related to:

https://bugzilla.ubuntu.com/show_bug.cgi?id=4764

As I had those same symptoms even when it "worked" after a reboot :)

i installed the debug packages and did some tracing.

a backtrace of the hung nautilus:

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7c0501e in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb766371d in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#3 0xb7666fa6 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
#4 0xb7666e7d in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0
#5 0xb767a076 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#6 0xb76a547d in Bonobo_ActivationContext_activateMatchingFull ()
   from /usr/lib/libbonobo-activation.so.4
#7 0xb76a72da in bonobo_activation_activate ()
   from /usr/lib/libbonobo-activation.so.4
#8 0xb76a75ef in bonobo_activation_activate_from_id ()
   from /usr/lib/libbonobo-activation.so.4
#9 0xb775d50e in activate_daemon (client=0x817a810) at gnome-vfs-client.c:213
#10 0xb775d69c in _gnome_vfs_client_get_daemon (client=0x817a810)
    at gnome-vfs-client.c:260
#11 0xb777ecf0 in gnome_vfs_volume_monitor_client_class_init (class=0x81638e8)
    at gnome-vfs-volume-monitor-client.c:83
#12 0xb77b6dd0 in g_type_free_instance () from /usr/lib/libgobject-2.0.so.0
#13 0xb77b8108 in g_type_class_ref () from /usr/lib/libgobject-2.0.so.0
#14 0xb77a3eff in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#15 0xb77a4243 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#16 0xb77a37d8 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#17 0xb777f7cd in _gnome_vfs_get_volume_monitor_internal (create=1)
    at gnome-vfs-volume-monitor.c:250
#18 0xb777f81a in gnome_vfs_get_volume_monitor ()
    at gnome-vfs-volume-monitor.c:277
#19 0x0806741e in nautilus_application_instance_init (application=0x8162ee8)
    at nautilus-application.c:164
#20 0xb77b60e5 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
#21 0xb77a4299 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#22 0xb7707bf3 in bonobo_object_query_local_interface ()
   from /usr/lib/libbonobo-2.so.0
#23 0xb77a3ac2 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#24 0xb77a4243 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#25 0xb77a37d8 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#26 0x080674e4 in nautilus_application_new () at nautilus-application.c:192
#27 0x080776bd in main (argc=2, argv=0xbffff8e4) at nautilus-main.c:318

and of gnome-panel (seems to be the same place):

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb78bd01e in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb772271d in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#3 0xb7725fa6 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
#4 0xb7725e7d in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0
#5 0xb7739076 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#6 0xb7c9a47d in Bonobo_ActivationContext_activateMatchingFull ()
   from /usr/lib/libbonobo-activation.so.4
#7 0xb7c9c2da in bonobo_activation_activate ()
   from /usr/lib/libbonobo-activation.so.4
#8 0xb7c9c5ef in bonobo_activation_activate_from_id ()
   from /usr/lib/libbonobo-activation.so.4
#9 0xb7d1f50e in activate_daemon...

*** Bug 11307 has been marked as a duplicate of this bug. ***

*** Bug 11448 has been marked as a duplicate of this bug. ***

*** Bug 11107 has been marked as a duplicate of this bug. ***

seems to be related to the dbus restart:
http://bugzilla.gnome.org/show_bug.cgi?id=161997

workaround for people getting this : "killall gnome-panel gnome-vfs-daemon
nautilus trashapplet drivemount_applet2"

BTW I've uploaded a new gnome-vfs2 without hal, let me know if you still get
this bug with it.

(In reply to comment #6)
> seems to be related to the dbus restart:
> http://bugzilla.gnome.org/show_bug.cgi?id=161997
>
> workaround for people getting this : "killall gnome-panel gnome-vfs-daemon
> nautilus trashapplet drivemount_applet2"
>
> BTW I've uploaded a new gnome-vfs2 without hal, let me know if you still get
> this bug with it.

(In reply to comment #6)

It's still there (on amd64) after dist-upgrade. Anything I can do to help debug it?

Great works ubuntu-folk!

have you restarted the box ?

Yes.

Since the last update to gnome-vfs I have had a hattrick of successful logins,
it seems to work.

Thanks for your time!

sorry to be the bearer of bad news, but i just had the problem again, after a
cold boot.

gnome-panel: 2.9.3-0ubuntu1
gnome-vfs2: 2.9.2-0ubuntu3

doing the "killall gnome-panel gnome-vfs-daemon nautilus trashapplet
drivemount_applet2"
fixes it.

*** Bug 11545 has been marked as a duplicate of this bug. ***

could you get a backtrace of the problem with the current versions ? I have no
problem since the hal support is off but getting a backtrace
could be useful, perhaps that's a different issue now

it seems to happen in the same place. here are the backtraces for
gnome-panel, nautilus and gnome-vfs-daemon.

gnome-panel:

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb78bf00e in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb772471d in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#3 0xb7727fa6 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
#4 0xb7727e7d in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0
#5 0xb773b076 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#6 0xb7d182fc in GNOME_VFS_Daemon_registerVolumeMonitor (_obj=0xfffffffc,
    client=0x8236f08, ev=0xfffffffc) at GNOME_VFS_Daemon-stubs.c:414
#7 0xb7d4265c in gnome_vfs_volume_monitor_client_class_init (class=0x8236590)
    at gnome-vfs-volume-monitor-client.c:87
#8 0xb77aedd0 in g_type_free_instance () from /usr/lib/libgobject-2.0.so.0
#9 0xb77b0108 in g_type_class_ref () from /usr/lib/libgobject-2.0.so.0
#10 0xb779beff in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#11 0xb779c243 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#12 0xb779b7d8 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#13 0xb7d430f1 in _gnome_vfs_get_volume_monitor_internal (create=1)
    at gnome-vfs-volume-monitor.c:250
#14 0xb7d4313e in gnome_vfs_get_volume_monitor ()
    at gnome-vfs-volume-monitor.c:277
#15 0x08087309 in panel_menu_bar_instance_init (menubar=0x8234120,
    klass=0x814f6d0) at panel-menu-bar.c:693
#16 0xb77ae0e5 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
#17 0xb779c299 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#18 0xb779bac2 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#19 0xb779c243 in g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
#20 0xb779b7d8 in g_object_new () from /usr/lib/libgobject-2.0.so.0
#21 0x080876bd in panel_menu_bar_load (panel=0x8164488, locked=1, position=0,
    exactpos=1, id=0xb77c1708 "$\006\003") at panel-menu-bar.c:878
#22 0x0807134b in panel_applet_load_idle_handler (dummy=0x0) at applet.c:834
#23 0xb7671a83 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#24 0xb766ed7a in g_main_depth () from /usr/lib/libglib-2.0.so.0
#25 0xb766fd2e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb7670050 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb767059a in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#28 0xb7acd39c in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#29 0x0806384f in main (argc=2, argv=0xbffffc24) at main.c:93

gnome-vfs-daemon:

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7a8d20b in __lll_mutex_lock_wait ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7a8a690 in _L_mutex_lock_26 () from /lib/tls/i686/cmov/libpthread.so.0
#3 0x08065f90 in ?? ()
#4 0x080b0d9c in ?? ()
#5 0x00000000 in ?? ()
#6 0xbfffed68 in ?? ()
#7 0xb7fd4b8c in __JCR_LIST__ () from /usr/lib/libgnomevfs-2.so.0
#8 0xbfffeec0 in ?? ()
#9 0xbfffed78 in ?? ()
#10 0xb7fbc067 in _gnome_vfs_get_volume_monitor_internal (create=-1208132224)
    at gnome-vfs-volume-monitor.c:244
#11 0xb7fbc067 in _gnome_vfs_get_volume_monitor_internal (create=1)
    at gnome-vfs-volume-m...

I got a similar problem too. To solve that I have removed my session
($HOME/gnome2/sesssion) and everything work fine after rebooting.

If I save the session again before leaving the desktop I fall again in the
problem ... and I have to remove my session agin ...

Don't know if it can help.

should be fixed for hoary

Workaround I successfully used with a 100% success rate to get around this is:

  sudo pkill -u $USER

and re-login when GDM provides a new login-dialogue.

  -Paul

*** Bug 11750 has been marked as a duplicate of this bug. ***

It seems to have become more frequent the last few days.

I still see this. (AMD64)

Clearing .gnome2/session* and .gnome2/.gnome-sm* and then killing stuff seems to
help.

does anybody here still get this issue/is able to get the lock somewhere ?

I've put a patched version of gnome-vfs2 that might fix this issue here (i386
deb and sources): http://people.ubuntu.com/~seb128/vfs/

any feedback on this would be welcome

I've uploaded the patched version in the archive:

 gnome-vfs2 (2.9.3-0ubuntu2) hoary; urgency=low
 .
   * debian/patches/14_vfsdaemonlock.patch:
     - upstream patch to fix the gnome-panel/nautilus freeze (Hoary: #4794).

Please let me know if you get the issue after restarting and while using these
packages.

i haven't had the problem since the update (a few reboots later, which would
have caused it previously, but now doesn't).

thanks

nice, thanks for the feedback. Seems to be fixed, I'm closing the bug. Feel free
to reopen if that happens again.

Still in Dapper!
After dist-upgrading from breeze yesterday my system become unusable. Gnome panel doesn't display anything except menu and does not respond to mouse clicks. Also nautilus keeps refreshing itself constantly.
Problem dissapears if I log on to newly created account.