Bug 617270 - [abrt] crash in epiphany-2.30.2-1.fc13: raise: Process /usr/bin/epiphany was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in epiphany-2.30.2-1.fc13: raise: Process /usr/bin/epiphany was ...
Keywords:
Status: CLOSED DUPLICATE of bug 596513
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b5d39733b02edfeae8a830d9095...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-22 16:02 UTC by Jorge Gallegos
Modified: 2010-11-09 16:02 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (33.31 KB, text/plain)
2010-07-22 16:02 UTC, Jorge Gallegos 		no flags Details
View All

Description Jorge Gallegos 2010-07-22 16:02:34 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: epiphany
comment: All plugins are deactivated via the preferences dialog in epiphany, but it still crashes while on pages with flash in them
component: epiphany
crash_function: raise
executable: /usr/bin/epiphany
global_uuid: b5d39733b02edfeae8a830d90957bd8336b194f3
kernel: 2.6.33.6-147.fc13.i686.PAE
package: epiphany-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Open epiphany
2. Go to any place with a flash object
3. Crash and burn
Comment 1 Jorge Gallegos 2010-07-22 16:02:36 UTC 
Created attachment 433745 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:02:09 UTC 

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

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