Bug 587867 - [abrt] crash in firefox-3.6.2-1.fc13: Process /usr/lib/firefox-3.6.2/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.6.2-1.fc13: Process /usr/lib/firefox-3.6.2/firefox ...
Status: CLOSED DUPLICATE of bug 543165
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:48049e61c64c0f8d14133890164...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-01 09:08 UTC by mohamed nasr
Modified: 2010-05-08 15:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-08 15:13:00 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (57.42 KB, text/plain)
2010-05-01 09:09 UTC, mohamed nasr
no flags Details

Description mohamed nasr 2010-05-01 09:08:56 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6.2/firefox
component: firefox
executable: /usr/lib/firefox-3.6.2/firefox
kernel: 2.6.33.1-24.fc13.i686.PAE
package: firefox-3.6.2-1.fc13
rating: 3
reason: Process /usr/lib/firefox-3.6.2/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 mohamed nasr 2010-05-01 09:09:04 UTC
Created attachment 410650 [details]
File: backtrace

Comment 2 Chris Campbell 2010-05-08 15:13:00 UTC
Thank you for taking the time to submit this bug report.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** 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.