thunderbird-bin crashed with SIGSEGV in PL_HandleEvent()

[KGB666]

Binary package hint: thunderbird

Description: Ubuntu jaunty (development branch)
Release: 9.04
thunderbird:
  Installé : 2.0.0.21+nobinonly-0ubuntu1
  Candidat : 2.0.0.21+nobinonly-0ubuntu1
 Table de version :
 *** 2.0.0.21+nobinonly-0ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Tryed to send email, but a crash occured after an error saying that he can not acces the smtp server.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/thunderbird/thunderbird-bin
Package: thunderbird 2.0.0.21+nobinonly-0ubuntu1
ProcCmdline: /usr/lib/thunderbird/thunderbird-bin
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: thunderbird
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/thunderbird/libxpcom_core.so
 PL_HandleEvent ()
Title: thunderbird-bin crashed with SIGSEGV in PL_HandleEvent()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
nsMsgAsyncWriteProtocol::UnblockPostReader (
nsMsgProtocolStreamProvider::OnOutputStreamReady (
nsOutputStreamReadyEvent::EventHandler (
PL_HandleEvent (self=0x39cfb28) at plevent.c:688

[bigal50 (bigal50)]

Had excatly the same problem with sending mail to my ISP's smtp server but was not at home so I was not logged into their networ, in my case Charter. The only difference is I am using a Latitude 620 which is not AMD64 or 64 bit.

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 353069, and any other logs that are relevant for this particular issue.

[Przemek K. (azrael)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
If you decide to reopen this bug, it would help us a lot if you could test the current Ubuntu development version (10.10) and check if this bug is still relevant.
Thanks again!