GNOME Bugzilla – Bug 489482
crash in Home Folder: Dateisuche
Last modified: 2007-10-25 12:31:37 UTC
What were you doing when the application crashed? Dateisuche 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 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 486932480 vsize: 486932480 resident: 46694400 share: 27561984 rss: 46694400 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193154394 rtime: 967 utime: 787 stime: 180 cutime:4 cstime: 3 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 2727)] [New Thread 1126189392 (LWP 3178)] (no debugging symbols found) 0x00000037916c82e6 in poll () from /lib64/libc.so.6
+ Trace 172286
Thread 2 (Thread 1126189392 (LWP 3178))
----------- .xsession-errors --------------------- (nautilus:2990): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x380005b (OpenOffice) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --- Hash table keys for warning below: --> file:///home/Dietmar (nautilus:3075): 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:3171): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2727): 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 ***