GNOME Bugzilla – Bug 515682
crash in Tasks: Nothing. The program was...
Last modified: 2008-02-11 10:53:20 UTC
Version: 2.10 What were you doing when the application crashed? Nothing. The program was downloading the "every 10 minutes" mails from our POP server and crashed Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 127991808 vsize: 127991808 resident: 59117568 share: 28229632 rss: 59117568 rss_rlim: 4294967295 CPU usage: start_time: 1202703156 rtime: 1236 utime: 1029 stime: 207 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 -1208920352 (LWP 2864)] [New Thread -1229591664 (LWP 2932)] [New Thread -1240081520 (LWP 2894)] [New Thread -1219101808 (LWP 2891)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188786
Thread 4 (Thread -1219101808 (LWP 2891))
----------- .xsession-errors (19 sec old) --------------------- (evolution:2864): camel-WARNING **: Could not find key entry for word 'd4safhgemp4vxguaayawbl6egbzghjj': Success (evolution:2864): camel-WARNING **: Could not find key entry for word 'gaaad4r4dxgemp4vxguaaxgpbl6eea9ghjj': Success (evolution:2864): camel-WARNING **: Could not find key entry for word 'd4sodbgemp4vxguaaagmbl6eqaxghjj': Success (evolution:2864): camel-WARNING **: Could not find key entry for word '05000000000000000000': Success (evolution:2864): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset --------------------------------------------------
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 339602 ***