GNOME Bugzilla – Bug 311440
Crashes on particular e-mail
Last modified: 2013-09-13 00:48:37 UTC
Steps to reproduce: 1. Load the e-mail in the attachment (see below) 2. View the e-mail (either by opening it or through the preview pane) 3. Watch it crash. Stack trace: stack trace:
+ Trace 61973
Output in the console window: (evolution-2.4:24797): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed camel-ERROR **: file camel-internet-address.c: line 331 (camel_internet_address_get): assertion failed: (CAMEL_IS_INTERNET_ADDRESS(addr)) aborting... Program received signal SIGABRT, Aborted. The e-mail source will be attached after posting the bug. Other information: This was popped off gmail. What's crashing is that the 'from' address in the message structure becomes NULL somewhere along the way, and this eventually gets passed to camel_internet_address_get. camel_internet_address_get tries to asser that addr is a valid camel internet address, and fails due to addr=0x0. This addr is supposed to be the 'from' address at this point. In this message, there are 2 'From:' headers. One has an e-mail address with valid syntax, the other (which comes later) has nothing after it.
Created attachment 49694 [details] e-mail source that caused Evolution to crash If you load this into an existing folder (either a newly created one with only this message or append it to one with messages already in it), it will show up. Then, after viewing it, Evolution will crash. It seems the whole message (or at least most of it) is necessary to crash Evolution.
Oh, one other thing. This crash has been happening since May 2005. I'm using some of the latest stuff from CVS (at least from July 18, 2005) and it's still crashing. I don't know enough about the mailer component (or e-mail formatting), or I'd try to create a patch for it myself.
workaround: turn off the setting "load images if sender in addressbook"
Created attachment 49859 [details] [review] fix this bug almost certainly has duplicates too
patch applied
*** Bug 309453 has been marked as a duplicate of this bug. ***
*** Bug 314395 has been marked as a duplicate of this bug. ***