abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin component: thunderbird crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib64/thunderbird-3.0/thunderbird-bin kernel: 2.6.32.19-163.fc12.x86_64 package: thunderbird-3.0.6-1.fc12 rating: 3 reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) time: 1282851138 uid: 500 How to reproduce ----- 1. somewhere in the process of emailing a snippet that i copied from a kde.org bug report page 2. 3.
Created an attachment (id=441317) File: backtrace
note that when i re-launched thunderbird that the state of the preview window had toggled
*** Bug 631937 has been marked as a duplicate of this bug. ***
closed duplicate (https://bugzilla.redhat.com/show_bug.cgi?id=631937) of this bug#627742 which had been opened to get the backtrace of later occurence logged.
*** Bug 637337 has been marked as a duplicate of this bug. ***
closed duplicate (https://bugzilla.redhat.com/show_bug.cgi?id=637337) of this bug#627742 noting both have random interesting bit relating to stack in 'nsImapProtocol.cpp:1342' "#5 nsImapProtocol::ImapThreadMainLoop (this=0x7f6e3463d000) at /usr/src/debug/thunderbird-3.0.6/comm-1.9.1/mailnews/imap/src/nsImapProtocol.cpp:1342 mon = Asked for position 0 of stack, stack only has 0 elements on it."
the "nsImapProtocol.cpp:1342" has 'accessing empty stack' snipet which also occurs in previously reported bug#621351. so closing this bug (bug#627742) as a duplicate of that earlier bug (bug#621351) *** This bug has been marked as a duplicate of bug 621351 ***