Bug 630128 - [abrt] thunderbird-3.1.2-1.fc13: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.2-1.fc13: Process /usr/lib64/thunderbird-3.1/thunderbi...
Keywords:
Status: CLOSED DUPLICATE of bug 615570
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:837b2ac2d8d9528002c0477b942...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-03 18:41 UTC by Scott Castaline
Modified: 2010-11-09 15:45 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (199.50 KB, text/plain)
2010-09-03 18:41 UTC, Scott Castaline
no flags Details

Description Scott Castaline 2010-09-03 18:41:39 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.6-47.fc13.x86_64
package: thunderbird-3.1.2-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: 1283528968
uid: 500

comment
-----
System was idle when I noticed that Thunderbird wasn't running anymore. I then noticed the red
light icon for abrt and found that it had crashed. So I am not sure as to what had happened or what
caused it to crash.

Comment 1 Scott Castaline 2010-09-03 18:41:41 UTC
Created an attachment (id=442957)
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:45:19 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:45:19 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 #615570.

Sorry for the inconvenience.


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