Bug 639324 - [abrt] thunderbird-3.1.4-1.fc13: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.4-1.fc13: Process /usr/lib64/thunderbird-3.1/thunderbi...
Keywords:
Status: CLOSED DUPLICATE of bug 608474
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c6d5bf563a84813a5ae54a02b3e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-01 12:59 UTC by Mark Dalton
Modified: 2010-11-09 14:16 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:16:04 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (73.80 KB, text/plain)
2010-10-01 12:59 UTC, Mark Dalton 		no flags Details
View All

Description Mark Dalton 2010-10-01 12:59:17 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.1/thunderbird-bin
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/thunderbird-3.1/thunderbird-bin
kernel: 2.6.34.7-56.fc13.x86_64
package: thunderbird-3.1.4-1.fc13
rating: 4
reason: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285937682
uid: 500

How to reproduce
-----
1. Machine was in suspend
2. Openned it up this morning, connected to the network
3. Read a few messages.
4. I was deleting the second message and it crashed.
Comment 1 Mark Dalton 2010-10-01 12:59:18 UTC 
Created attachment 450999 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:16:04 UTC 

*** This bug has been marked as a duplicate of bug 608474 ***
Comment 3 Karel Klíč 2010-11-09 14:16:04 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 #608474.

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