After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 526138 - Forwading Email causes crash - new composer
Forwading Email causes crash - new composer
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
: 526595 (view as bug list)
Depends on:
Blocks: 522153
 
 
Reported: 2008-04-04 12:20 UTC by Reid Thompson
Modified: 2013-09-13 00:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Reid Thompson 2008-04-04 12:20:43 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 ()

Thread 1 (Thread 0xb66506d0 (LWP 1164))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at ../../../glib/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at ../../../glib/glib/gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 segv_redirect
    at ../../../evolution/shell/main.c line 519
  • #9 <signal handler called>
  • #10 IA__g_type_check_instance_cast
    at ../../../glib/gobject/gtype.c line 3177
  • #11 forward_attached
    at ../../../evolution/mail/em-composer-utils.c line 878
  • #12 forward_attached_cb
    at ../../../evolution/mail/em-composer-utils.c line 889
  • #13 do_build_attachment
    at ../../../evolution/mail/mail-ops.c line 1168
  • #14 get_messages_done
    at ../../../evolution/mail/mail-ops.c line 1848
  • #15 mail_msg_idle_cb
    at ../../../evolution/mail/mail-mt.c line 503
  • #16 g_idle_dispatch
    at ../../../glib/glib/gmain.c line 4087
  • #17 g_main_dispatch
    at ../../../glib/glib/gmain.c line 2009
  • #18 IA__g_main_context_dispatch
    at ../../../glib/glib/gmain.c line 2561
  • #19 g_main_context_iterate
    at ../../../glib/glib/gmain.c line 2642
  • #20 IA__g_main_loop_run
    at ../../../glib/glib/gmain.c line 2850
  • #21 bonobo_main
    at bonobo-main.c line 311
  • #22 main
    at ../../../evolution/shell/main.c line 782
  • #0 __kernel_vsyscall


----------- .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>
Comment 1 Matthew Barnes 2008-04-04 12:24:11 UTC
Adding this to the "new composer" tracker (bug #522153).
Comment 2 Matthew Barnes 2008-04-06 21:57:25 UTC
*** Bug 526595 has been marked as a duplicate of this bug. ***
Comment 3 Matthew Barnes 2008-04-07 04:10:34 UTC
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.
Comment 4 Matthew Barnes 2008-04-07 04:12:21 UTC
To clarify: s/simply make it/simply make camel_header_unfold()/