GNOME Bugzilla – Bug 508833
crash in Tasks: Evolution crashed when I...
Last modified: 2008-02-06 08:18:02 UTC
Version: 2.10 What were you doing when the application crashed? Evolution crashed when I was closing the app after reading IMAP messages. 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve-Slate Icon Theme: HighContrast Memory status: size: 120467456 vsize: 120467456 resident: 50663424 share: 34922496 rss: 50663424 rss_rlim: 4294967295 CPU usage: start_time: 1200080636 rtime: 1138 utime: 1044 stime: 94 cutime:1 cstime: 2 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 -1208346912 (LWP 5629)] [New Thread -1350583408 (LWP 5822)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 184973
Thread 2 (Thread -1350583408 (LWP 5822))
----------- .xsession-errors --------------------- (evolution:5629): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed (evolution:5629): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream' (evolution:5629): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:5629): camel-CRITICAL **: camel_stream_printf: assertion `CAMEL_IS_STREAM (stream)' failed (evolution:5629): camel-WARNING **: Trying to check junk data is OBJECT 'CamelStream' (evolution:5629): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:5629): camel-CRITICAL **: camel_stream_write: assertion `CAMEL_IS_STREAM (stream)' failed Setting up initial mail tree addressbook_migrate (0.0.0) --------------------------------------------------
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 440451 ***