thunderbird-bin crashed with SIGSEGV

[[e-mail]]

Binary package hint: thunderbird

100% reproducible crash while displaying the attached email. Just open it in T-bird with "open saved message" and use the mouse wheel to scroll down. When you scroll to about the mid-point of the message t-bird crashes.

I manually changed the email addresses in the attachment, but that doesn't effect the crash.

ProblemType: Crash
Architecture: i386
Date: Tue Jun 3 11:20:42 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/thunderbird/thunderbird-bin
NonfreeKernelModules: nvidia
Package: thunderbird 2.0.0.14+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: i386
ProcCmdline: /usr/lib/thunderbird/thunderbird-bin
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: thunderbird
StacktraceTop:
 ?? () from /usr/lib/thunderbird/components/libgklayout.so
 ?? () from /usr/lib/thunderbird/components/libgklayout.so
 ?? () from /usr/lib/thunderbird/components/libgklayout.so
 ?? () from /usr/lib/thunderbird/components/libgklayout.so
 ?? () from /usr/lib/thunderbird/components/libgklayout.so
Title: thunderbird-bin crashed with SIGSEGV
Uname: Linux 2.6.24-17-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner users video

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/thunderbird/components/libgklayout.so
?? () from /usr/lib/thunderbird/components/libgklayout.so
?? () from /usr/lib/thunderbird/components/libgklayout.so
?? () from /usr/lib/thunderbird/components/libgklayout.so
?? () from /usr/lib/thunderbird/components/libgklayout.so

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Jonathan Thomas (echidnaman)]

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". Thanks again!