Bug 675704

Summary: [abrt] epiphany-1:2.30.6-1.fc14: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Clément DAVID <c.david86>
Component: epiphanyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gecko-bugs-nobody, rob.townley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:63ec7adab011a2d5adfc2f62d324c5c8b2d3e9f3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 09:29:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Clément DAVID 2011-02-07 13:16:42 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: epiphany --sm-client-id 10ee5c8f53fbd8a364129602696018797300000019640056 --load-session /home/davidcl/.gnome2/epiphany/session_gnome-GIYWPV.xml
component: epiphany
crash_function: WebCore::PrintContext::spoolPage
executable: /usr/bin/epiphany
kernel: 2.6.35.10-74.fc14.x86_64
package: epiphany-1:2.30.6-1.fc14
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297084455
uid: 500

How to reproduce
-----
1. go to https://computing.llnl.gov/tutorials/parallel_comp/
2. Crash when trying to print

Comment 1 Clément DAVID 2011-02-07 13:16:45 UTC
Created attachment 477408 [details]
File: backtrace

Comment 2 Martin Stransky 2012-02-15 09:29:44 UTC
We're using mozilla crash reporter tool which reports crashes directly to mozilla crash database now, ABRT is no longer used for mozilla packages.

This is an automated bug change. If you can reproduce the crash reliably (you have testcase, page where it crashes or so), please reopen this bug and assign it directly to me.

Thanks.