abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin comment: The crash happens every time I click on my imap account. It never happens with my POP account. Both are configured in Thunderbird. For me, it is 100% reproducable. Thanks. component: thunderbird executable: /usr/lib64/thunderbird-3.0/thunderbird-bin kernel: 2.6.32.10-90.fc12.x86_64 package: thunderbird-3.0.4-1.fc12 rating: 4 reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 405547 [details] File: backtrace
How to reproduce ----- 1.Open Thunderbird 2.Wait a few seconds 3.Click through the numerous error notice boxes then it craps out Comment ----- The errors mentioned above are ones implying there is an error with retrieving information for the welcome to thunderbird page nothing earth shattering here as they were allways there even before this bigger issue arose
How to reproduce ----- 1. Given my configuration, just start it. 2. Enter passwords 3. Try and read your mail. It crashes before you can get to the right tab.
How to reproduce ----- 1.Moved old .thunderbird out of the way 2.Restarted thunderbird 3.Configured accounts 4.Went to read mail. Crashed.
So ... it's not an issue with cruft in my old .thunderbird directory. Adding more-or-less the same accounts results in the same issue.
How to reproduce ----- 1. Start Thunderbird 2. Window opens and synchronization to mail accounts starts 3. Window closes and crash Comment ----- When invoked from the command line, the following crash note is displayed: /usr/lib64/thunderbird-3.0/run-mozilla.sh: line 131: 4375 Segmentation fault (core dumped) "$prog" ${1+"$@"}
*** Bug 592800 has been marked as a duplicate of this bug. ***
as filer of bug 592800 there is one additional point I'd like to make: Thunderbird works fine for all of my imap accounts except aol.com( AIM ). If I do not add the aol account, all other accounts work fine with no crashes. This is from a fresh install of Fedora and Ubuntu. I assume the 64bit versions of TB are built by the respective distros. So, since both distros have the same issues then I would assume it is source code of TB or a common lib, but I'm just guessing. the aim(aol) settings are: imap.aol.com SSL smtp.aol.com TSL
I see the same as Chris Hodge. I added back all my accounts, and it crashed. I started over and added all my accounts except for AOL Imap, and it still works.
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
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.