GNOME Bugzilla – Bug 521793
crash in Tasks: Attempting to disable an...
Last modified: 2008-05-13 11:45:33 UTC
Version: 2.10 What were you doing when the application crashed? Attempting to disable an account 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 139206656 vsize: 139206656 resident: 48025600 share: 35840000 rss: 48025600 rss_rlim: 4294967295 CPU usage: start_time: 1205247273 rtime: 534 utime: 493 stime: 41 cutime:3 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 -1208387872 (LWP 32496)] [New Thread -1353008240 (LWP 32528)] [New Thread -1266685040 (LWP 32517)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 192085
Thread 1 (Thread -1208387872 (LWP 32496))
----------- .xsession-errors (71245 sec old) --------------------- (evolution:3801): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:3801): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:3801): camel-CRITICAL **: camel_object_unhook_event: assertion `CAMEL_IS_OBJECT (obj)' failed (evolution:3801): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:3801): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:3801): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed (evolution:3801): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' ...Too much output, ignoring rest... --------------------------------------------------
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 324168 ***