Evolution crash when opening a mail

Bug #63094 reported by Etienne Goyer
12
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Critical
evolution (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs
gtk+2.0 (Ubuntu)
Fix Released
Medium
Kees Cook

Bug Description

Not sure if this is related to #58365 ...

Evolution crash when opening the mail in attachment.

evolution_2.8.0-0ubuntu3 and evolution-data-server-dbg_1.8.0-0ubuntu1 on Edgy.

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :
Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :
Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

I had sent a Bug Buddy report the first time I experienced the problem. The bug that was open automatically just got classified as a duplicate of 353430 on bugzilla.gnome.org, so there is no point in reporting upstream. I guess this one can be closed too, but I will leave it open for now since I am not quite sure.

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's a GTK bug according to upstream: http://bugzilla.gnome.org/show_bug.cgi?id=353430

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Changed in gtk:
status: Unknown → Confirmed
Revision history for this message
Fabián Rodríguez (magicfab) wrote :

This in turn makes it impossible to open Evolution is the preview default to the message causing the crash. I checked the upstream report and it contained this tip to be able to start Evolution in such cases and to simply prevent rendering of the mail.

You can disable the preview pane using this command:
gconftool-2 --set /apps/evolution/mail/display/show_preview --type bool 0

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Checked the upstream bug. It seems many new duplicate bugs are being reported upstream.

Changed in evolution:
assignee: nobody → desktop-bugs
status: Unconfirmed → Rejected
Revision history for this message
Daniel Holbach (dholbach) wrote :

I just closed the evolution task. The gtk+2.0 part is still valid.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

It appears that the latest gtk security update fixes this issue. I tried the crasher listed in the evolution report and upstream and evolution did not crash.

Revision history for this message
Kees Cook (kees) wrote :

Thanks for testing! I'd agree based on the upstream back-traces: this is the same issue fixed in the GDK pixbuf loader. Do other people find that the gtk update solves this problem for them?

Revision history for this message
Kees Cook (kees) wrote :

For reference, the update was USN-415-1.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Kees, in what distribution has that one been fixed? Do you have some changelog entry for the upload? The upstream bug has not been marked fixed yet

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

Work for me, thanks !

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

Etienne can you confirm you checked it in Edgy ? Anyone reporting this as "Works for Me" (WFM), don't forget to specify your version.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

In the update tool this is referred to as security update CVE-2007-0010 in Edgy as of today.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0010

Revision history for this message
Etienne Goyer (etienne-goyer-outlands) wrote :

Indeed, Edgy it is.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

WFM Dapper

Revision history for this message
Kees Cook (kees) wrote :
Changed in gtk:
status: Confirmed → Needs Info
Revision history for this message
Kees Cook (kees) wrote :

Closing, this appears to be fixed.

Changed in gtk+2.0:
assignee: desktop-bugs → keescook
status: Confirmed → Fix Released
Changed in gtk:
status: Needs Info → Fix Released
Changed in gtk:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.