GNOME Bugzilla – Bug 502916
crash in Tasks: Closing an open email.
Last modified: 2007-12-13 12:33:30 UTC
Version: 2.10 What were you doing when the application crashed? Closing an open email. 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.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: Clearlooks Icon Theme: Fedora Memory status: size: 191672320 vsize: 191672320 resident: 69947392 share: 45420544 rss: 69947392 rss_rlim: 4294967295 CPU usage: start_time: 1197318313 rtime: 3324 utime: 3030 stime: 294 cutime:82 cstime: 24 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 -1208564000 (LWP 16246)] [New Thread -1319109744 (LWP 16315)] [New Thread -1253180528 (LWP 16263)] [New Thread -1242301552 (LWP 16262)] 0x004ca991 in waitpid () from /lib/libpthread.so.0
+ Trace 181482
Thread 1 (Thread -1208564000 (LWP 16246))
----------- .xsession-errors --------------------- 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 239441 ***