Bug 615551 - [abrt] crash in firefox-3.6.4-1.fc13: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
[abrt] crash in firefox-3.6.4-1.fc13: Process /usr/lib/firefox-3.6/firefox wa...
Status: CLOSED DUPLICATE of bug 612329
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:dbbcc7decfde0c1f07b4937a0f3...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-16 23:39 EDT by Bruce
Modified: 2010-11-09 09:41 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 09:41:39 EST
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 (97.68 KB, text/plain)
2010-07-16 23:39 EDT, Bruce
no flags Details

  None (edit)
Description Bruce 2010-07-16 23:39:48 EDT
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox https://bugzilla.redhat.com/show_bug.cgi?id=615457
comment: Mozilla crashes in an updated Fedore 11-13
component: firefox
executable: /usr/lib/firefox-3.6/firefox
global_uuid: dbbcc7decfde0c1f07b4937a0f37f67b280dcf77
kernel: 2.6.33.3-85.fc13.i686
package: firefox-3.6.4-1.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Bruce 2010-07-16 23:39:53 EDT
Created attachment 432534 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 09:41:39 EST

*** This bug has been marked as a duplicate of bug 612329 ***
Comment 3 Karel Klíč 2010-11-09 09:41:39 EST
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 #612329.

Sorry for the inconvenience.

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