Bug 652949

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

Description Jovan Chekalov 2010-11-13 18:29:46 UTC
abrt version: 1.1.13
architecture: i686
cmdline: epiphany
component: epiphany
executable: /usr/bin/epiphany
kernel: 2.6.35.6-48.fc14.i686
package: epiphany-1:2.30.5-1.fc14
rating: 3
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289670611
uid: 500

backtrace
-----
[New Thread 2080]
[New Thread 2081]
[New Thread 2089]
[New Thread 2090]
Core was generated by `epiphany'.
Program terminated with signal 11, Segmentation fault.
#0  0x00200074 in big5_2charset () from /usr/lib/libX11.so.6

Timeout exceeded: 60 second, killing gdb
Debuginfo absent: 8396e45af3d34c321b02c5e1f98b1af327ba7603

How to reproduce
-----
1. clicked twice in the address bar to select all text
2.
3.

Comment 1 Jovan Chekalov 2010-11-13 18:29:49 UTC
Created attachment 460261 [details]
File: backtrace

Comment 2 Martin Stransky 2012-02-15 09:30:25 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.