GNOME Bugzilla – Bug 544299
crash in Open Folder: Browsing network
Last modified: 2008-07-26 09:20:47 UTC
Version: 2.20.0 What were you doing when the application crashed? Browsing network Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 73494528 vsize: 73494528 resident: 20922368 share: 14282752 rss: 20922368 rss_rlim: 4294967295 CPU usage: start_time: 1216806486 rtime: 229 utime: 210 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b54720 (LWP 2749)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 203560
Thread 1 (Thread 0xb6b54720 (LWP 2749))
----------- .xsession-errors (65 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/Debian:/tmp/.ICE-unix/2671 ** (gnome-settings-daemon:2726): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/kevin/.metacity/sessions/default0.ms: Failed to open file '/home/kevin/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 72732672 vsize: 72732672 resident: 21295104 share: 14290944 rss: 21295104 rss_rlim: 4294967295 CPU usage: start_time: 1216968222 rtime: 264 utime: 234 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6b94720 (LWP 2735)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 203742
Thread 1 (Thread 0xb6b94720 (LWP 2735))
----------- .xsession-errors (85 sec old) --------------------- ![1216969805,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969805,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969807,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969807,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969809,000,xklavier_evt_xkb.c:xkl_xkb_process_x_even (synaptic:2811): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed t/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969809,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969813,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969813,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969815,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969815,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969820,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1216969820,000,xklavier ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***