Bug 623845 - [abrt] crash in epiphany-2.30.2-1.fc13: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
[abrt] crash in epiphany-2.30.2-1.fc13: Process /usr/bin/epiphany was killed ...
Status: CLOSED DUPLICATE of bug 610058
Product: Fedora
Classification: Fedora
Component: epiphany (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:5e1fdb8cd5e4d776d7ef56b2c5f...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-12 19:48 EDT by Tobias Mueller
Modified: 2010-11-09 09:12 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 09:12:58 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 (56.25 KB, text/plain)
2010-08-12 19:48 EDT, Tobias Mueller
no flags Details

  None (edit)
Description Tobias Mueller 2010-08-12 19:48:37 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: epiphany -p
component: epiphany
crash_function: WebCore::PluginPackage::fetchInfo
executable: /usr/bin/epiphany
global_uuid: 5e1fdb8cd5e4d776d7ef56b2c5f76444fc7fa87b
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: epiphany-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. opened epiphany and browsed a random webpage, i.e. skyscanner.net
2.
3.
Comment 1 Tobias Mueller 2010-08-12 19:48:41 EDT
Created attachment 438562 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 09:12:58 EST

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

Sorry for the inconvenience.

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