abrt 1.0.6 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: evolution comment: When offending email, which was a regular newsletter from military.com, evolution would crash. The way I resolved it was to quickly delete two mails in a row, the second was the offending email. I suspect that the crash was occurring when evolution was processing the preview window. If you want the email I still have it in my gmail account. Thank you. component: evolution executable: /usr/bin/evolution kernel: 2.6.31.12-174.2.3.fc12.x86_64 package: evolution-2.28.2-1.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine) How to reproduce ----- 1.Simply select offending mail in inbox 2. 3.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #1) > This message is a reminder that Fedora 12 is nearing its end of life. > Approximately 30 (thirty) days from now Fedora will stop maintaining > and issuing updates for Fedora 12. It is Fedora's policy to close all > bug reports from releases that are no longer maintained. At that time > this bug will be closed as WONTFIX if it remains open with a Fedora > 'version' of '12'. > > Package Maintainer: If you wish for this bug to remain open because you > plan to fix it in a currently maintained version, simply change the 'version' > to a later Fedora version prior to Fedora 12's end of life. > > Bug Reporter: Thank you for reporting this issue and we are sorry that > we may not be able to fix it before Fedora 12 is end of life. If you > would still like to see this bug fixed and are able to reproduce it > against a later version of Fedora please change the 'version' of this > bug to the applicable version. If you are unable to change the version, > please add a comment here and someone will do it for you. > > Although we aim to fix as many bugs as possible during every release's > lifetime, sometimes those efforts are overtaken by events. Often a > more recent Fedora release includes newer upstream software that fixes > bugs or makes them obsolete. > > The process we are following is described here: > http://fedoraproject.org/wiki/BugZappers/HouseKeeping I have not had this issue occur recently. And as I no longer have any of the mail messages that caused this problem I cannot verify that the problem is fixed, therefore I must assume that it has been fixed and you can close this bug report. Randy Boyd
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.