GNOME Bugzilla – Bug 480308
crash in Home Folder: Datei gesucht
Last modified: 2007-09-29 00:41:44 UTC
What were you doing when the application crashed? Datei gesucht 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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 485756928 vsize: 485756928 resident: 43180032 share: 27111424 rss: 43180032 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190741037 rtime: 285 utime: 260 stime: 25 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496344112 (LWP 5504)] [New Thread 1094719824 (LWP 5534)] (no debugging symbols found) 0x00000037916c82e6 in poll () from /lib64/libc.so.6
+ Trace 165422
Thread 2 (Thread 1094719824 (LWP 5534))
----------- .xsession-errors --------------------- (bug-buddy:5496): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:5496): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --- Hash table keys for warning below: --> file:///home/Dietmar (nautilus:5512): 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/Dietmar (nautilus:5525): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:5504): 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 ***