GNOME Bugzilla – Bug 487654
crash in Tasks:
Last modified: 2007-10-22 23:12:35 UTC
Version: 2.10 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.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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 368902144 vsize: 368902144 resident: 261595136 share: 36921344 rss: 261595136 rss_rlim: 4294967295 CPU usage: start_time: 1192570892 rtime: 20253 utime: 19922 stime: 331 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208808720 (LWP 30597)] [New Thread -1349084272 (LWP 31475)] [New Thread -1256490096 (LWP 31236)] [New Thread -1246467184 (LWP 30703)] (no debugging symbols found) 0x005b5991 in waitpid () from /lib/libpthread.so.0
+ Trace 170950
Thread 2 (Thread -1349084272 (LWP 31475))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x15a3aef X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x65 warning: the debug information found in "/usr/lib/debug//usr/lib/gconv/ISO8859-1.so.debug" does not match "/usr/lib/gconv/ISO8859-1.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/gconv/CP1252.so.debug" does not match "/usr/lib/gconv/CP1252.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/gnome-vfs-2.0/modules/libfile.so.debug" does not match "/usr/lib/gnome-vfs-2.0/modules/libfile.so" (CRC mismatch). --------------------------------------------------
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 445309 ***