thunderbird-bin crashed with SIGSEGV in raise() after moving email

[John Paulett]

Binary package hint: thunderbird

I just moved two emails from my trash folder back to my inbox by dragging them into the inbox. I am using IMAP in Thunderbird version 2.0.0.4 (20070618) in Gutsy.

The error is reproducible, it occurs when I try to drag any email into any folder.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Jul 1 09:20:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/thunderbird/thunderbird-bin
NonfreeKernelModules: nvidia ath_hal
Package: thunderbird 2.0.0.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/thunderbird/thunderbird-bin
ProcCwd: /home/mpt
ProcEnviron:
 PATH=/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:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
Title: thunderbird-bin crashed with SIGSEGV in raise()
Uname: Linux caesar 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

[Hilario J. Montoliu (hjmf) (hmontoliu)]

Retrace done.

Extract from retraced stacktrace:
...
#0 ?? ()
#1 ?? ()
#2 ?? ()
#3 ?? ()
#4 flockfile () from /lib/tls/i686/cmov/libpthread.so.0
#5 ?? ()
#6 ?? ()
#7 nsProfileLock::FatalSignalHandler (signo=-1210642444) at nsProfileLock.cpp:206

Backtrace stopped: previous frame inner to this frame (corrupt stack?)
...

Tagging as mt-needtestcase, mt-waitdup for further processing

[Hilario J. Montoliu (hjmf) (hmontoliu)]

Retraced Thread Stacktrace

[Hilario J. Montoliu (hjmf) (hmontoliu)]

Thank you for the bug report however this report lacks information we need to investigate it further. Of course this is not your fault, but the retrace obtained from your report doesn't provide useful information for us as it seems to be corrupted. For this reason, we are now going to close the bug report - please feel free to reopen when you have more information at hand.

And please don't doubt to report any other crashes/issues you might have in the future.

Further information can be found at [1].

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs