GNOME Bugzilla – Bug 541219
crash in Evolution Mail:
Last modified: 2008-07-03 04:35:27 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 41394176 vsize: 41394176 resident: 13103104 share: 10702848 rss: 13103104 rss_rlim: 4294967295 CPU usage: start_time: 1214996913 rtime: 18 utime: 14 stime: 4 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb684c6d0 (LWP 4528)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201897
Thread 1 (Thread 0xb684c6d0 (LWP 4528))
----------- .xsession-errors --------------------- (evolution:4508): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:4508): libsoup-CRITICAL **: soup_message_set_flags: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:4508): libsoup-CRITICAL **: soup_session_send_message: assertion `SOUP_IS_MESSAGE (msg)' failed CalDAV Eplugin starting up ... get itn\pooja exchange://itn%5cpooja;auth=Basic@owa.itn.local/ Find Items 0 (evolution:4528): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:4528): libsoup-CRITICAL **: soup_message_set_flags: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:4528): libsoup-CRITICAL **: soup_session_send_message: assertion `SOUP_IS_MESSAGE (msg)' failed --------------------------------------------------
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 453932 ***