GNOME Bugzilla – Bug 510754
crash in Tasks:
Last modified: 2008-01-24 10:27:19 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 138461184 vsize: 138461184 resident: 48070656 share: 30224384 rss: 48070656 rss_rlim: 4294967295 CPU usage: start_time: 1200822382 rtime: 956 utime: 889 stime: 67 cutime:33 cstime: 10 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 -1209149728 (LWP 3727)] [New Thread -1312216176 (LWP 4514)] [New Thread -1311949936 (LWP 4012)] [New Thread -1272972400 (LWP 3999)] [New Thread -1260708976 (LWP 3748)] (no debugging symbols found) 0x00f31402 in __kernel_vsyscall ()
+ Trace 186047
Thread 1 (Thread -1209149728 (LWP 3727))
----------- .xsession-errors (22 sec old) --------------------- (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:3727): 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 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 447591 ***