GNOME Bugzilla – Bug 487929
crash in Home Folder: - click on toolbar icon ...
Last modified: 2007-10-18 16:58:36 UTC
What were you doing when the application crashed? - click on toolbar icon 'search' - search for string "Thumbs" - no result - language: de - the directory i searched in contained in subdirs files with invalid filename (german higher ascii > 127; copied from windows xp via scp) 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: Fedora Memory status: size: 471949312 vsize: 471949312 resident: 38797312 share: 21073920 rss: 38797312 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192720388 rtime: 3326 utime: 3128 stime: 198 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 2606)] [New Thread 1147169104 (LWP 3000)] (no debugging symbols found) 0x00000038c28c82e6 in poll () from /lib64/libc.so.6
+ Trace 171158
Thread 2 (Thread 1147169104 (LWP 3000))
----------- .xsession-errors --------------------- localuser:tebas being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2491 --- Hash table keys for warning below: --> file:///home/tebas (nautilus:2701): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2606): 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 ***