GNOME Bugzilla – Bug 483607
crash in Home Folder: Doing a search in file m...
Last modified: 2007-10-05 14:32:19 UTC
What were you doing when the application crashed? Doing a search in file manager 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: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 119463936 vsize: 119463936 resident: 47067136 share: 32681984 rss: 47067136 rss_rlim: 4294967295 CPU usage: start_time: 1191564756 rtime: 550 utime: 500 stime: 50 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 -1209051424 (LWP 2245)] [New Thread -1232643184 (LWP 4410)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 167897
Thread 2 (Thread -1232643184 (LWP 4410))
----------- .xsession-errors (7 sec old) --------------------- 08:31:27 : Population Completed --- Hash table keys for warning below: --> file:///home/mah/.Trash --> file:///home/mah (nautilus:4394): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above) --- Hash table keys for warning below: --> file:///home/mah/.Trash --> file:///home/mah (nautilus:4403): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above) (nautilus:2245): 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 ***