GNOME Bugzilla – Bug 560707
crash in Open Folder: Just logged back in afte...
Last modified: 2008-11-14 19:30:14 UTC
Version: 2.20.0 What were you doing when the application crashed? Just logged back in after display sleep. Have USB flash drive mounted. Opening home folder. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Raleigh Icon Theme: gnome Memory status: size: 88502272 vsize: 88502272 resident: 20201472 share: 11988992 rss: 20201472 rss_rlim: 4294967295 CPU usage: start_time: 1226536065 rtime: 2810 utime: 2514 stime: 296 cutime:34 cstime: 13 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 0xb6a86710 (LWP 2781)] (no debugging symbols found) 0xb7f76424 in __kernel_vsyscall ()
+ Trace 209752
Thread 1 (Thread 0xb6a86710 (LWP 2781))
----------- .xsession-errors (9 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) warning: could not initiate dbus current dist not found in meta-release file (glade-3:3235): Gdk-CRITICAL **: gdk_window_set_icon: assertion `GDK_WINDOW_TYPE (window) != GDK_WINDOW_CHILD' failed (glade-3:3235): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (glade-3:3235): Gdk-CRITICAL **: gdk_window_set_icon: assertion `GDK_WINDOW_TYPE (window) != GDK_WINDOW_CHILD' failed (glade-3:3235): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed ** ** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0) --------------------------------------------------
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 356672 ***