GNOME Bugzilla – Bug 587136
crash in Evolution Mail and Calendar: Sending an email.
Last modified: 2009-06-27 15:57:51 UTC
What were you doing when the application crashed? Sending an email. Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.24.3 2009-06-13 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.27-gentoo-r8 #1 SMP PREEMPT Tue Mar 10 23:38:03 CET 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 138887168 vsize: 138887168 resident: 55357440 share: 25780224 rss: 55357440 rss_rlim: 18446744073709551615 CPU usage: start_time: 1246114026 rtime: 995 utime: 890 stime: 105 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb570b720 (LWP 23820)] [New Thread 0xaded6b90 (LWP 23899)] [New Thread 0xb49ffb90 (LWP 23882)] [New Thread 0xb2afcb90 (LWP 23880)] 0xb7ff8424 in __kernel_vsyscall ()
+ Trace 216216
Thread 1 (Thread 0xb570b720 (LWP 23820))
----------- .xsession-errors (1115 sec old) --------------------- (17:31:39) util: Writing file /home/vladms/.purple/accounts.xml (17:31:39) soap: read 14154 bytes (17:31:39) soap: current HTTP/1.1 200 OK Date: Sat, 27 Jun 2009 14:31:39 GMT Server: Microsoft-IIS/6.0 P3P:CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo" X-Powered-By: ASP.NET X-MSNSERVER: BY2ABCHWB341 X-AspNet-Version: 2.0.50727 Cache-Control: private, max-age=0 Content-Type: text/xml; charset=utf-8 Content-Length: 13841 <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLS ...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 535516 ***