abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: claws-mail comment: I was deleting (Shift-Canc) a message from my IMAP account (gmail) component: claws-mail crash_function: folder_item_get_msginfo_by_msgid executable: /usr/bin/claws-mail kernel: 2.6.34.6-47.fc13.i686.PAE package: claws-mail-3.7.6-1.fc13 rating: 4 reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1283876845 uid: 500
Created an attachment (id=443912) File: backtrace
Package: claws-mail-3.7.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- I was deleting a message from my gmail account.
*** Bug 620845 has been marked as a duplicate of this bug. ***
Package: claws-mail-3.7.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- I was deleting (Shift+Canc) a message from my IMAP (gmail) account.
*** Bug 667320 has been marked as a duplicate of this bug. ***
*** Bug 662227 has been marked as a duplicate of this bug. ***
*** Bug 544906 has been marked as a duplicate of this bug. ***
In response to Michael Schwendt (https://bugzilla.redhat.com/show_bug.cgi?id=667320). > could be much more verbose, please? Unfortunately the bug is quite random (IOW, deleting a message works most of the times) and I do not know how to further detail my report. Are you referring to any specific info I can provide to help track the problem down? Regards. Alessandro
No, primarly I wanted to learn that there is no special keyboard shortcut (or such) that might be relevant. And the confirmation that it is _not_ 100% reproducible for you, that it does not crash always when trying to delete a message. In bug 667320 all that was obvious. There is a problem in Claws Mail related to interrupting busy IMAP connections (in various ways), and I think Claws Mail ought to become able to protect itself against running into such conditions.
*** Bug 678363 has been marked as a duplicate of this bug. ***
*** Bug 693942 has been marked as a duplicate of this bug. ***
*** Bug 711339 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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