Description of problem:
I attempt to send an email in Thunderbird, but my SMTP server results in an
error message (untrusted MTA). After the error message shows, Thunderbird
crashes, and bug-buddy loads with a generated bug report.
Version-Release number of selected component (if applicable):
Every time the error message appears, thunderbird crashes.
Steps to Reproduce:
1. Set up a default smtp server that will result in the "untrusted MTA" error
2. Compose a message, and send it
Thunderbird crashes, and message is lost.
I was actually expecting no error message (still haven't figured out why the MTA
is untrusted), but the expected results when the error message does appear is to
be able to click OK, and return to composition window. In addition, it is also
expected that if the program does crash, I will be able to resume the
composition of the message that was typed up. (Perhaps the message could be
saved in Local Folders->unsent messages).
Created attachment 304567 [details]
bug-buddy generated bug report
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue. Unfortunately the bug-buddy report, you have
provided is currently not yet useful, we need to get it generated in the old way:
Please install firefox-debuginfo; in order to do this run
Then run thunderbird with a parameter -g. That will start thunderbird running
inside of gdb debugger. Then use command run and do whatever you did to make
thunderbird crash. When it happens, you should go back to the gdb and run
(gdb) thread apply all backtrace
This produces usually many screens of the text. Copy all of them into a text
editor and attach the file to the bug as an uncompressed attachment.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 304701 [details]
Requested debugging output attached.
NOTE: The bug did not occur in exactly the same way as when I run it without
gdb. Without gdb, it initiates bug-buddy and shuts down after bug-buddy closes.
When using gdb, it does not initiate bug-buddy (I assume this is normal), but
it does not close down on it's own either... the windows stay up (main and
compose windows) and hang (stop redrawing, don't respond to close, etc.)
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.
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 9'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 9 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:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.