GNOME Bugzilla – Bug 469391
crash in Tasks:
Last modified: 2007-08-23 03:34:39 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.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 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: 120766464 vsize: 120766464 resident: 39424000 share: 31166464 rss: 39424000 rss_rlim: 4294967295 CPU usage: start_time: 1187816965 rtime: 222 utime: 209 stime: 13 cutime:2 cstime: 5 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 -1208215840 (LWP 2764)] [New Thread -1269834864 (LWP 2854)] [New Thread -1225798768 (LWP 2804)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157214
Thread 1 (Thread -1208215840 (LWP 2764))
----------- .xsession-errors (18 sec old) --------------------- localuser:kelvin being added to access control list SESSION_MANAGER=local/kcv-home.zft.co.uk:/tmp/.ICE-unix/2551 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... (evolution:2764): evolution-shell-WARNING **: Cannot activate 'OAFIID:GNOME_Evolution_Exchange_Component:2.10': Child process did not give an error message, unknown failure occurred ** (evolution:2764): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2764): DEBUG: mailto URL program: evolution (evolution:2764): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:2764): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
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 ***