Bug 646987 - [abrt] thunderbird-3.1.4-1.fc13: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.4-1.fc13: Process /usr/lib/thunderbird-3.1/thunderbird...
Keywords:
Status: CLOSED DUPLICATE of bug 612049
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 13
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3d85e039a6f30f6cc57d943987d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-26 19:27 UTC by Alan Schmidt
Modified: 2010-11-09 13:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:54:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (75.41 KB, text/plain)
2010-10-26 19:27 UTC, Alan Schmidt
no flags Details

Description Alan Schmidt 2010-10-26 19:27:33 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.1/thunderbird-bin
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/thunderbird-3.1/thunderbird-bin
kernel: 2.6.34.7-61.fc13.i686.PAE
package: thunderbird-3.1.4-1.fc13
rating: 4
reason: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1288119012
uid: 500

How to reproduce
-----
1.Reboot Cyrus IMAP server
2.After an hour or so with Thunderbird running all this time, 
and only looking at mail on a different account, click on the inbox of the IMAP server
which had been rebooted.

Comment 1 Alan Schmidt 2010-10-26 19:27:35 UTC
Created attachment 455852 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:54:54 UTC

*** This bug has been marked as a duplicate of bug 612049 ***

Comment 3 Karel Klíč 2010-11-09 13:54:54 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #612049.

Sorry for the inconvenience.


Note You need to log in before you can comment on or make changes to this bug.