Bug 632820 - [abrt] firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 626409
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2b9cc7126ea0baa12cda18cd743...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-11 07:38 UTC by valentingushchin@yandex.ru
Modified: 2010-11-09 14:33 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (85.87 KB, text/plain)
2010-09-11 07:39 UTC, valentingushchin@yandex.ru 		no flags Details
View All

Description valentingushchin@yandex.ru 2010-09-11 07:38:58 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale ru --sm-config-prefix /firefox-oCfZPI/ --sm-client-id 10c9796472000128415832500000019900046 --screen 0
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.34.6-54.fc13.x86_64
package: firefox-3.6.7-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1284190594
uid: 500
Comment 1 valentingushchin@yandex.ru 2010-09-11 07:39:02 UTC 
Created an attachment (id=446631)
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:33:05 UTC 

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

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