GNOME Bugzilla – Bug 499991
crash in Tasks: Just trying to pick up m...
Last modified: 2007-11-27 19:45:42 UTC
Version: 2.10 What were you doing when the application crashed? Just trying to pick up my e-mail. 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: 120659968 vsize: 120659968 resident: 26697728 share: 15597568 rss: 26697728 rss_rlim: 4294967295 CPU usage: start_time: 1196176036 rtime: 1365 utime: 1022 stime: 343 cutime:1808 cstime: 163 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 -1208359200 (LWP 12570)] [New Thread -1260975216 (LWP 12671)] [New Thread -1272972400 (LWP 12600)] [New Thread -1239995504 (LWP 12598)] [New Thread -1229505648 (LWP 12593)] [New Thread -1219015792 (LWP 12592)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 179833
Thread 2 (Thread -1260975216 (LWP 12671))
----------- .xsession-errors (99 sec old) --------------------- (evolution:12570): camel-WARNING **: Could not find key entry for word 'tglqusqdvohtpkuxlhjlotpgsqgllv2vs': Invalid argument (evolution:12570): camel-WARNING **: Could not find key entry for word 'tglqusqdvohtpkuxlhjlotpgsqgllv2vt': Invalid argument (evolution:12570): camel-WARNING **: Could not find key entry for word 'tglqusqdvohtpkuxlhjlotpgsqgllv2vw': Invalid argument (evolution:12570): camel-WARNING **: Could not find key entry for word 'tglqusqdvohtpkuxlhjlotpgsqgllv2vy': Invalid argument (evolution:12570): camel-WARNING **: Could not find key entry for word 'tglqwtqsdvohtpkuxlhjlotpgsqgllv2vsb': Invalid or incomplete multibyte or wide character --------------------------------------------------
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 ***