GNOME Bugzilla – Bug 479459
crash in Tasks:
Last modified: 2007-09-23 11:46:32 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 152305664 vsize: 152305664 resident: 66011136 share: 34553856 rss: 66011136 rss_rlim: 4294967295 CPU usage: start_time: 1190532264 rtime: 2702 utime: 1991 stime: 711 cutime:2 cstime: 6 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 -1208207648 (LWP 3854)] [New Thread -1281799280 (LWP 4132)] [New Thread -1228805232 (LWP 3906)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164799
Thread 1 (Thread -1208207648 (LWP 3854))
----------- .xsession-errors (425 sec old) --------------------- (evolution:3854): camel-WARNING **: Could not find key entry for word 'उउ琼扡敬戠牯敤㵲': Invalid argument (evolution:3854): camel-WARNING **: Could not find key entry for word '芀ऊउउउ㰉琯㹤': Invalid argument (evolution:3854): camel-WARNING **: Could not find key entry for word 'उउउउ琼㹲琼': Invalid argument (evolution:3854): camel-WARNING **: Could not find key entry for word '㸠ऊउउ琼㹲琼': Invalid argument (evolution:3854): camel-WARNING **: Could not find key entry for word '㸠ऊउउउ㰉牴㸠琼': Invalid argument --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431459 ***