abrt 1.0.0 detected a crash. Comment: Selecting new unread email after deleting an unread email. Attached file: backtrace cmdline: claws-mail component: claws-mail executable: /usr/bin/claws-mail kernel: 2.6.31.6-145.fc12.i686.PAE package: claws-mail-3.7.3-1.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 376544 [details] File: backtrace
*** Bug 544967 has been marked as a duplicate of this bug. ***
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
this still happens at random intervals under F13 (claws-mail-3.7.6-1.fc13.x86_64) Over the next few weeks I'll know if it's gotten better under F14 (claws-mail-3.7.6-1.fc14.1.x86_64)
Since this has not been tracked appropriately and initially referred to F12 with a backtrace that has changed meanwhile, I'm closing this as duplicate of a much newer bug. *** This bug has been marked as a duplicate of bug 631090 ***