GNOME Bugzilla – Bug 505963
crash in Tasks:
Last modified: 2008-01-10 04:14:58 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.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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 138203136 vsize: 138203136 resident: 57712640 share: 35020800 rss: 57712640 rss_rlim: 4294967295 CPU usage: start_time: 1198273180 rtime: 4218 utime: 3719 stime: 499 cutime:32 cstime: 23 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 -1208768800 (LWP 3023)] [New Thread -1300481136 (LWP 4554)] [New Thread -1268343920 (LWP 32305)] [New Thread -1228051568 (LWP 3139)] [New Thread -1217553520 (LWP 3070)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183260
Thread 2 (Thread -1300481136 (LWP 4554))
----------- .xsession-errors --------------------- (evolution:3023): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error (evolution:3023): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error (evolution:3023): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error (evolution:3023): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error (evolution:3023): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error camel-ERROR **: file camel-partition-table.c: line 872 (camel_key_table_lookup): assertion failed: (index < kb->used) aborting... in emp_apps_open_in in emp_apps_open_in --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system and partially fixed, but please feel free to report any further bugs you find. Please comment #122 in bug 348149 *** This bug has been marked as a duplicate of 348149 ***