GNOME Bugzilla – Bug 468568
crash in File Browser: What's up?!!!!!! I can'...
Last modified: 2007-08-21 20:28:54 UTC
Version: 2.18.3 What were you doing when the application crashed? What's up?!!!!!! I can't look for a file because it is happen 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 86528000 vsize: 86528000 resident: 32612352 share: 21286912 rss: 32612352 rss_rlim: 4294967295 CPU usage: start_time: 1187625982 rtime: 1757 utime: 1190 stime: 567 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 -1208432928 (LWP 3075)] [New Thread -1211040880 (LWP 3118)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156609
Thread 2 (Thread -1211040880 (LWP 3118))
----------- .xsession-errors --------------------- (bug-buddy:3068): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:3068): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:3068): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:3068): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --- Hash table keys for warning below: --> file:///root (nautilus:3085): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3075): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x98c1)! --------------------------------------------------
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 ***