When previewing or viewing a particular message, evolution crashes/aborts with these messages on the console: (evolution-2.6:5170): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (evolution-2.6:5170): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (evolution-2.6:5170): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion `pixbuf != NULL' failed GdkPixbuf-ERROR **: file io-gif.c: line 984 (gif_get_lzw): assertion failed: (gdk_pixbuf_get_has_alpha (context->frame->pixbuf)) aborting... This is FC5 x86_64 with evolution-2.6.3-1.fc5.5 and gtk2-2.8.20-1. I'm attaching the offending message. I also have it stored in a local folder, let me know if you want to take a look at that. WARNING: the message is spam, and one of the attachments (Cupid.gif, which I suppose is the one causing the problem) says it's base64 encoded, but doesn't look like valid base64 data. So I have no idea what it actually is, approach with caution.
Created attachment 135163 [details] The offending message, gzipped
Thanks for the bug report. I'll have a look (carefully).
Still crashes as of evolution-2.8.0-7.fc6.x86_64 and gtk2-2.10.4-4.fc6.x86_64, bumping to FC6.
Still crashes with evolution-2.8.2.1-2.fc6.x86_64, gtk2-2.10.4-6.fc6.x86_64
My apologies that I still have not investigated this one yet. I think I remember something like this being fixed in GTK+ recently. Can you please re-test with Fedora 8 Test 2 or later?
I don't have a F8t* box around at the moment, and I've also switched to kmail quite a while ago so I don't have a setup that I could test this with at the moment. However, I suppose it'd be fairly easy for you to test it - the gzipped message in comment 1 looks like one that can probably be imported to evolution as a mbox after gunzipping it.
Thanks for responding. Didn't see your attachment there; I was just doing a quick sweep over old bugs. I'll try to reproduce this for myself on F8.
Tested the message in comment #1 with Evolution 2.12 and GTK+ 2.12. You said you thought the data in the message was not valid Base64, and sure enough the image failed to load and Evolution displayed a missing image icon (red X) where it should have been. No crash either, so I'm going to close this.