GNOME Bugzilla – Bug 522841
crash in Evolution Mail:
Last modified: 2008-03-20 13:35:33 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.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Leopard_GTK_v0.2 Icon Theme: Aqua_Project Memory status: size: 581447680 vsize: 581447680 resident: 50774016 share: 23572480 rss: 50774016 rss_rlim: 18446744073709551615 CPU usage: start_time: 1205753079 rtime: 233 utime: 212 stime: 21 cutime:16 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2af16c3b8910 (LWP 31868)] [New Thread 0x44007950 (LWP 31883)] [New Thread 0x43806950 (LWP 31882)] [New Thread 0x42804950 (LWP 31880)] [New Thread 0x42003950 (LWP 31879)] [New Thread 0x41001950 (LWP 31877)] [New Thread 0x40800950 (LWP 31875)] 0x00002af161de634f in waitpid () from /lib/libpthread.so.0
+ Trace 192624
Thread 1 (Thread 0x2af16c3b8910 (LWP 31868))
----------- .xsession-errors --------------------- /home/john/.themes/Leopard_GTK_v0.2/gtk-2.0/Frame-Gap/frame1.png, borders don't fit within the image ** (evolution:31868): WARNING **: Invalid borders specified for theme pixmap: /home/john/.themes/Leopard_GTK_v0.2/gtk-2.0/Buttons/button-default.png, borders don't fit within the image get jbtlee exchange://jbtlee;auth=Basic@owa.massey.ac.nz/ Find Items 9 Couldn't Get password 9 (evolution:31868): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:31868): libsoup-CRITICAL **: soup_message_set_flags: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:31868): 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 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 361972 ***