GNOME Bugzilla – Bug 484170
crash in Computer: i was looking for a file...
Last modified: 2007-10-07 11:19:12 UTC
Version: 2.18.3 What were you doing when the application crashed? i was looking for a file using the CTRL+F search tool 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 103116800 vsize: 103116800 resident: 51134464 share: 21295104 rss: 51134464 rss_rlim: 4294967295 CPU usage: start_time: 1191682797 rtime: 596 utime: 544 stime: 52 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 -1208101152 (LWP 2422)] [New Thread -1242190960 (LWP 3710)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 168349
Thread 2 (Thread -1242190960 (LWP 3710))
----------- .xsession-errors (8 sec old) --------------------- (gsf-office-thumbnailer:3610): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --- Hash table keys for warning below: --> file:///home/arnaud (nautilus:3694): 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/arnaud (nautilus:3703): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2422): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x14397)! --------------------------------------------------
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 ***