GNOME Bugzilla – Bug 502007
crash in Tasks:
Last modified: 2007-12-06 19:12:44 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-10.fc7 #1 SMP Fri Oct 19 14:12:10 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: 182419456 vsize: 182419456 resident: 93859840 share: 29302784 rss: 93859840 rss_rlim: 4294967295 CPU usage: start_time: 1196939485 rtime: 1563 utime: 1333 stime: 230 cutime:1 cstime: 4 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 -1208834336 (LWP 3013)] [New Thread -1231234160 (LWP 3135)] [New Thread -1220187248 (LWP 3031)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180938
Thread 2 (Thread -1231234160 (LWP 3135))
----------- .xsession-errors --------------------- warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address (wrong library or version mismatch?) CalDAV Eplugin starting up ... ** (evolution:3013): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3013): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:3013): camel-WARNING **: Could not find key entry for word 'orsiotot00000008': Operation now in progress camel-ERROR **: file camel-partition-table.c: line 872 (camel_key_table_lookup): assertion failed: (index < kb->used) aborting... Xlib: unexpected async reply (sequence 0x9efa)! --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 348149 ***