GNOME Bugzilla – Bug 526138
Forwading Email causes crash - new composer
Last modified: 2013-09-13 00:59:50 UTC
Steps to reproduce: 1. Click on forward button 2. Crash 3. Stack trace: Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.20.3 2008-01-17 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.24-gentoo-r4 #1 SMP PREEMPT Mon Mar 31 12:07:10 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: marble-look Icon Theme: gnome Memory status: size: 149004288 vsize: 149004288 resident: 50520064 share: 22372352 rss: 50520064 rss_rlim: 4294967295 CPU usage: start_time: 1207310708 rtime: 835 utime: 750 stime: 85 cutime:123 cstime: 25 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/evo/bin/evolution' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb66506d0 (LWP 1164)] [New Thread 0xb232db90 (LWP 1662)] [New Thread 0xb175bb90 (LWP 1660)] [New Thread 0xb0759b90 (LWP 1277)] [New Thread 0xb2ffdb90 (LWP 1186)] [New Thread 0xb3fffb90 (LWP 1184)] 0xb7f1d410 in __kernel_vsyscall ()
+ Trace 194194
Thread 1 (Thread 0xb66506d0 (LWP 1164))
----------- .xsession-errors (234 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 -------------------------------------------------- Other information: had to post bug manually -- bug buddy failed with error..... Bug Buddy has encountered an error while submitting your report to the Bugzilla server. Details of the error are included below. Failed to parse the xml-rpc response. Response follows: Unable to parse XML-RPC Response 3 <?xml version="1.0" encoding="UTF-8"?> <methodResponse><fault><value><struct><member><name>faultString</name><value><string>Application failed during request deserialization: not well-formed (invalid token) at line 23, column 0, byte 1713 at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/XML/Parser.pm line 187 </string></value></member><member><name>faultCode</name><value><string>Client</string></value></member></struct></value></fault></methodResponse>
Adding this to the "new composer" tracker (bug #522153).
*** Bug 526595 has been marked as a duplicate of this bug. ***
This was a combination of an obvious bug and a not-so-obvious bug. The obvious bug was mine: - editor = GTKHTML_EDITOR (editor); + editor = GTKHTML_EDITOR (composer); The not-so-obvious bug was caused by this change: http://svn.gnome.org/viewvc/evolution/trunk/mail/em-format-quote.c?r1=35061&r2=35320 For me the crash was occurring on a message without a Reply-To header. In the very last hunk of the change, camel_medium_get_header(part, "Reply-To") returns NULL. That result now gets passed directly to camel_header_unfold(), which does not check for NULL. The solution was to simply make it return NULL if the input string is NULL. Fixed in Evolution-Data-Server revision 8623 and Evolution revision 35330.
To clarify: s/simply make it/simply make camel_header_unfold()/