Bug 614152 - [abrt] epiphany-2.31.3-2.fc14: raise: Process /usr/bin/epiphany was killed by signal 6 (SIGABRT)
Summary: [abrt] epiphany-2.31.3-2.fc14: raise: Process /usr/bin/epiphany was killed by...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2df888b1f1dec152eaffe0a3ca8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-13 18:46 UTC by Francisco Hauva
Modified: 2012-02-15 09:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-15 09:28:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (32.58 KB, text/plain)
2010-07-13 18:46 UTC, Francisco Hauva 		no flags Details
View All

Description Francisco Hauva 2010-07-13 18:46:44 UTC 
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: epiphany
component: epiphany
crash_function: raise
executable: /usr/bin/epiphany
global_uuid: 2df888b1f1dec152eaffe0a3ca8a09ee9e656a34
kernel: 2.6.35-0.31.rc4.git4.fc14.x86_64
package: epiphany-2.31.3-2.fc14
rating: 1
reason: Process /usr/bin/epiphany was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Rawhide)
time: 1279046266
uid: 500
Comment 1 Francisco Hauva 2010-07-13 18:46:51 UTC 
Created attachment 431551 [details]
File: backtrace
Comment 2 Bug Zapper 2010-07-30 12:33:00 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Martin Stransky 2012-02-15 09:28:22 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.
Note You need to log in before you can comment on or make changes to this bug.