Bug 646195 - [abrt] firefox-3.6.11-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] firefox-3.6.11-1.fc13: Process /usr/lib64/firefox-3.6/firefox was kill...
Keywords:
Status: CLOSED DUPLICATE of bug 543165
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:72983bb5595caa6dadb4cbd24d4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-24 22:56 UTC by Bernardo Barros
Modified: 2018-04-11 18:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-22 17:34:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (38.33 KB, text/plain)
2010-10-24 22:56 UTC, Bernardo Barros
no flags Details

Description Bernardo Barros 2010-10-24 22:56:01 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale pt-BR
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.34.7-61.fc13.x86_64
package: firefox-3.6.11-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: jut quit
time: 1287960543
uid: 500

Comment 1 Bernardo Barros 2010-10-24 22:56:04 UTC
Created attachment 455372 [details]
File: backtrace

Comment 2 Bernardo Barros 2010-10-25 01:22:52 UTC
Package: firefox-3.6.11-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
just quit

Comment 3 Bernardo Barros 2010-10-25 06:02:34 UTC
Package: firefox-3.6.11-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
Just quit again

Comment 4 Matěj Cepl 2010-12-22 17:34:16 UTC

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


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