Thunderbird 2.0.0.17 freezes randomly

[Mauricio Peñaloza S.]

Binary package hint: thunderbird

Hi, i had a Ubuntu Hardy 8.04 with kernel 2.6.24-21 generic, thunderbird 2.0.0.17 with enigmail 0.95.7 and lightning 0.7 a couple of weeks ago, it freezes when receive new mail (sometimes are digitally signed and sometimes not).
If you need more info please ask me.

ProblemType: Bug
Architecture: i386
Date: Tue Oct 7 10:29:57 2008
Dependencies:

DistroRelease: Ubuntu 8.04
NonfreeKernelModules: fglrx
Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list]
PackageArchitecture: all
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SourcePackage: thunderbird
Uname: Linux 2.6.24-21-generic i686

[firelord (frederik-cabo)]

Just for the record: I have the same problem with thunderbird 2.0.0.17, enigmail 0.95.7 and lightning 0.7 on an older Mandriva system with KDE-3.4.2 and kernel 2.6.17-15 on an Athlon.

[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 279648, 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!