GNOME Bugzilla – Bug 470427
crash in Home Folder: 搜索
Last modified: 2007-09-05 15:37:27 UTC
What were you doing when the application crashed? 搜索 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 124948480 vsize: 124948480 resident: 47243264 share: 28852224 rss: 47243264 rss_rlim: 4294967295 CPU usage: start_time: 1188130360 rtime: 741 utime: 632 stime: 109 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 -1208584480 (LWP 2500)] [New Thread -1275430000 (LWP 3002)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 157993
Thread 2 (Thread -1275430000 (LWP 3002))
----------- .xsession-errors --------------------- (file-roller:2970): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:2970): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:2970): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:2970): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:2970): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (file-roller:2970): Pango-CRITICAL **: pango_coverage_get: assertion `index >= 0' failed (nautilus:2500): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x9f77)! --------------------------------------------------
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 ***