GNOME Bugzilla – Bug 482287
crash in Tasks: emailing
Last modified: 2008-05-02 10:51:19 UTC
Version: 2.10 What were you doing when the application crashed? emailing 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 128098304 vsize: 128098304 resident: 46084096 share: 35086336 rss: 46084096 rss_rlim: 4294967295 CPU usage: start_time: 1191245282 rtime: 548 utime: 497 stime: 51 cutime:24 cstime: 7 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 -1209133344 (LWP 14084)] [New Thread -1310213232 (LWP 15680)] [New Thread -1252815984 (LWP 14716)] [New Thread -1281934448 (LWP 14714)] [New Thread -1231029360 (LWP 14103)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 166888
Thread 2 (Thread -1310213232 (LWP 15680))
----------- .xsession-errors (522 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Error (0): PDF file is damaged - attempting to reconstruct xref table... (evince:15501): Gtk-WARNING **: Unsupported unit (evince:15501): Gtk-WARNING **: Unsupported unit (evolution:14084): camel-WARNING **: Could not find key entry for word 'office': No such file or directory camel-ERROR **: file camel-partition-table.c: line 872 (camel_key_table_lookup): assertion failed: (index < kb->used) aborting... index:0 in emp_apps_open_in set language en-US --------------------------------------------------
*** Bug 489432 has been marked as a duplicate of this bug. ***
*** Bug 502149 has been marked as a duplicate of this bug. ***
*** Bug 502307 has been marked as a duplicate of this bug. ***
*** Bug 516163 has been marked as a duplicate of this bug. ***
*** Bug 505368 has been marked as a duplicate of this bug. ***
*** Bug 518764 has been marked as a duplicate of this bug. ***
has it been fixed by bug 348149 ?
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 348149 ***