GNOME Bugzilla – Bug 508344
crash in Home Folder: pesquisando
Last modified: 2008-01-10 01:16:31 UTC
What were you doing when the application crashed? pesquisando 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: LiNsta-GTK2 Icon Theme: Vista-Inspirate_1.0 Memory status: size: 92012544 vsize: 92012544 resident: 34693120 share: 21151744 rss: 34693120 rss_rlim: 4294967295 CPU usage: start_time: 1199900263 rtime: 142 utime: 128 stime: 14 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 -1208191264 (LWP 25670)] [New Thread -1233130608 (LWP 25681)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184698
Thread 2 (Thread -1233130608 (LWP 25681))
----------- .xsession-errors --------------------- SFX q gir je-o tossir warning - incompatible stripping characters and condition: SFX q gir je-os tossir warning - incompatible stripping characters and condition: SFX q gir je-se tossir warning - incompatible stripping characters and condition: SFX q gir je-te tossir warning - incompatible stripping characters and condition: SFX q gir je-vos tossir (nautilus:2934): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x4c1bb)! (nautilus:25670): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0xf82)! --------------------------------------------------
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 ***