GNOME Bugzilla – Bug 521547
crash in Tasks:
Last modified: 2008-03-10 15:48:19 UTC
Version: 2.10 What were you doing when the application 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 138235904 vsize: 138235904 resident: 46305280 share: 34643968 rss: 46305280 rss_rlim: 4294967295 CPU usage: start_time: 1205147168 rtime: 328 utime: 264 stime: 64 cutime:0 cstime: 0 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 -1208244512 (LWP 23060)] [New Thread -1255228528 (LWP 23081)] [New Thread -1244333168 (LWP 23070)] [New Thread -1233843312 (LWP 23064)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191953
Thread 4 (Thread -1233843312 (LWP 23064))
----------- .xsession-errors (13 sec old) --------------------- (evolution:23060): camel-WARNING **: Could not find key entry for word 'юридические': El carácter multibyte o extendido está incompleto o es inválido (evolution:23060): camel-WARNING **: Could not find key entry for word 'юридические': El carácter multibyte o extendido está incompleto o es inválido (evolution:23060): camel-WARNING **: Could not find key entry for word 'введение': El carácter multibyte o extendido está incompleto o es inválido (evolution:23060): camel-WARNING **: Could not find key entry for word 'введение': El carácter multibyte o extendido está incompleto o es inválido (evolution:23060): camel-WARNING **: Could not find key entry for word 'введение': El carácter multibyte o extendido está incompleto o es inválido --------------------------------------------------
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 ***