Bug 651014 - [abrt] firefox-3.5.15-1.fc12: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.5.15-1.fc12: Process /usr/lib64/firefox-3.5/firefox was kill...
Keywords:
Status: CLOSED DUPLICATE of bug 543165
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1c95dc41a0c74815148f6a6a1bc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-08 16:27 UTC by Pedro
Modified: 2010-11-09 16:19 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
File: backtrace (36.71 KB, text/plain)
2010-11-08 16:27 UTC, Pedro 		no flags Details
View All

Description Pedro 2010-11-08 16:27:08 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.5/firefox
kernel: 2.6.32.23-170.fc12.x86_64
package: firefox-3.5.15-1.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1289233431
uid: 500
Comment 1 Pedro 2010-11-08 16:27:11 UTC 
Created attachment 458796 [details]
File: backtrace
Comment 2 Morten Slott Hansen 2010-11-09 14:00:59 UTC 
Package: firefox-3.5.15-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. close ff
2.
3.
Comment 3 Karel Klíč 2010-11-09 16:19:49 UTC 

*** This bug has been marked as a duplicate of bug 543165 ***
Comment 4 Karel Klíč 2010-11-09 16:19:49 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 #543165.

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