Bug 801687

Summary: [abrt] stardict-3.0.1-22.fc14: Process /usr/bin/stardict was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: gjf <goujunfeng>
Component: stardictAssignee: anish <apatil>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: i18n-bugs, nav007, petersen, supercyper1, zhu
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7e7e7818a7f3bfce9d13fc75619e17f812eac2e0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-09 06:18:48 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 gjf 2012-03-09 07:02:19 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 22375 bytes
cmdline: stardict
component: stardict
Attached file: coredump, 49795072 bytes
executable: /usr/bin/stardict
kernel: 2.6.35.14-103.fc14.i686
package: stardict-3.0.1-22.fc14
rating: 3
reason: Process /usr/bin/stardict was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1331237329
uid: 500

How to reproduce
-----
1.It always crash when i start computer from "Hibernate"
2.
3.
Comment 1 gjf 2012-03-09 07:02:27 UTC 
Created attachment 568829 [details]
File: backtrace
Comment 2 Jens Petersen 2012-05-11 01:35:55 UTC 
Moving to new owner of current releases.

Anish, these bugs are currently still against Fedora 14.
It would be good to triage them more carefully when you have time
and then either move them to newer releases if fixable
or otherwise close.
Comment 3 anish 2012-07-09 06:17:44 UTC 
Can you please try to reproduce this issue on Fedora 17. If this issue still exists in latest version , steps to reproduce to this issue will be appriciated.
I am closing this bug. We can reopen it if issue persists in latest version.