GNOME Bugzilla – Bug 468025
crash in Home Folder: in
Last modified: 2007-08-21 20:24:28 UTC
What were you doing when the application crashed? in Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nova-Blue Icon Theme: Fedora Memory status: size: 93085696 vsize: 93085696 resident: 28098560 share: 21164032 rss: 28098560 rss_rlim: 4294967295 CPU usage: start_time: 1187465613 rtime: 315 utime: 289 stime: 26 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 -1208596768 (LWP 4179)] [New Thread -1211544688 (LWP 4255)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156204
Thread 2 (Thread -1211544688 (LWP 4255))
----------- .xsession-errors --------------------- (bug-buddy:4160): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:4160): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --- Hash table keys for warning below: --> file:///home/jonny (nautilus:4227): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/jonny (nautilus:4248): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:4179): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 454799 ***