GNOME Bugzilla – Bug 498583
crash in Home Folder: noting
Last modified: 2007-11-24 18:40:04 UTC
What were you doing when the application crashed? noting Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Amaranth Icon Theme: Amaranth Memory status: size: 119042048 vsize: 119042048 resident: 42725376 share: 26112000 rss: 42725376 rss_rlim: 4294967295 CPU usage: start_time: 1195587127 rtime: 9956 utime: 9565 stime: 391 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208387872 (LWP 3801)] [New Thread -1210754160 (LWP 4137)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178983
Thread 1 (Thread -1208387872 (LWP 3801))
----------- .xsession-errors (310 sec old) --------------------- (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:3801): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed ...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 436071 ***