GNOME Bugzilla – Bug 436248
Viewing a Spam message with a gif-File crashes evolution ((gif_get_lzw): assertion failed)
Last modified: 2007-07-02 05:11:51 UTC
Steps to reproduce: Steps to reproduce (and workaround): 1. Start evolution with evolution --component=2 & 2. Click on Contacts or Calendar and then File -> New -> E-Mail Folder 3. Create a new folder 4. Click on E-Mail and on the folder the corrupted message is in (not the new one). 5. evolution crashes, but in the background you can see the address and the subject (memorize these) 6. Search in .evolution/mail/local/ for the folder. 7. open the file with an editor, search for the address or subject and delete the gif section. Safe the file. 8. Open evolution, some error messages or shown (synchronization errors). After the next start those should be gone. Delete the one created folder. Stack trace: (evolution-2.6:3613): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (evolution-2.6:3613): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `pixbuf != NULL' failed (evolution-2.6:3613): 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... Program received signal SIGABRT, Aborted.
+ Trace 132640
Thread NaN (LWP 3613)
Other information: I get a lot of spam. I go through the spam directory and delete each one pressing "del", so that the next one gets highlighted. Today evolution crashed. The message contained a gif-image. It looks like the bug is related to libgtk2.0-0 but I am not sure. If so, could somebody please reassign it. The justification for the severity is, that since that messages was marked, every time starting evolution again made it crash, since it wanted to display that message. Originally reported by Paul Menzel <paul.menzel@web.de> at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402990
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!