GNOME Bugzilla – Bug 516416
crash in Tasks:
Last modified: 2008-02-14 18:20:23 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 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: 154562560 vsize: 154562560 resident: 56860672 share: 42557440 rss: 56860672 rss_rlim: 4294967295 CPU usage: start_time: 1202986028 rtime: 1424 utime: 1308 stime: 116 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 -1209116960 (LWP 3411)] [New Thread -1256203376 (LWP 3441)] [New Thread -1289536624 (LWP 3439)] [New Thread -1245713520 (LWP 3431)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189164
Thread 1 (Thread -1209116960 (LWP 3411))
----------- .xsession-errors (94 sec old) --------------------- (evolution:3411): camel-WARNING **: Could not find key entry for word 'disposición': Conseguido (evolution:3411): camel-WARNING **: Could not find key entry for word 'deleitarán': Conseguido (evolution:3411): camel-WARNING **: Could not find key entry for word 'rodean': Conseguido (evolution:3411): camel-WARNING **: Could not find key entry for word 'imagines': Conseguido (evolution:3411): camel-WARNING **: Could not find key entry for word 'acompañantes': Conseguido --------------------------------------------------
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 501900 ***