Bug 596261 - [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib64/firefox-3.5/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib64/firefox-3.5/firefox ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 11
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0029c70994c4f66fa0027dab018...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-26 13:33 UTC by Slawek Gawlowski
Modified: 2010-06-28 15:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 15:44:55 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (50.57 KB, text/plain)
2010-05-26 13:33 UTC, Slawek Gawlowski
no flags Details

Description Slawek Gawlowski 2010-05-26 13:33:15 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox http://w3.ibm.com/articles/workingknowledge/2010/05/anzswgcluster_clusternews_xunwangphd.html
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.5/firefox
global_uuid: 0029c70994c4f66fa0027dab01863e2e1ddacc90
kernel: 2.6.32.12-115.fc12.x86_64
package: firefox-3.5.9-2.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 11

Comment 1 Slawek Gawlowski 2010-05-26 13:33:21 UTC
Created attachment 416835 [details]
File: backtrace

Comment 2 Bug Zapper 2010-06-28 15:44:55 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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