GNOME Bugzilla – Bug 512808
crash in Tasks: I was forwarding an emai...
Last modified: 2008-01-29 23:11:00 UTC
Version: 2.10 What were you doing when the application crashed? I was forwarding an email. I hit enter a couple of times and then it crashed. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 210829312 vsize: 210829312 resident: 77398016 share: 49659904 rss: 77398016 rss_rlim: 4294967295 CPU usage: start_time: 1201616988 rtime: 4815 utime: 4469 stime: 346 cutime:76 cstime: 51 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208731936 (LWP 6460)] [New Thread -1242494064 (LWP 7048)] [New Thread -1329595504 (LWP 6584)] [New Thread -1263858800 (LWP 6503)] [New Thread -1210831984 (LWP 6500)] 0x004ca991 in waitpid () from /lib/libpthread.so.0
+ Trace 187205
Thread 1 (Thread -1208731936 (LWP 6460))
----------- .xsession-errors (20 sec old) --------------------- warning: the debug information found in "/usr/lib/debug//lib/libcrypt-2.6.so.debug" does not match "/lib/libcrypt.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib/libnss_files-2.6.so.debug" does not match "/lib/libnss_files.so.2" (CRC mismatch). 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//lib/libnss_nisplus-2.6.so.debug" does not match "/lib/libnss_nisplus.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib/libnss_dns-2.6.so.debug" does not match "/lib/libnss_dns.so.2" (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 458670 ***