Bug 592776

Summary: [abrt] crash in glista-0.4-3.fc12: Process /usr/bin/glista was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: javadieh <javadieh_msd>
Component: glistaAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:f425387feb45e8ff97a00116a0dec6b69d305843
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-05 16:29:52 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 javadieh 2010-05-16 20:55:42 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: glista
component: glista
executable: /usr/bin/glista
global_uuid: f425387feb45e8ff97a00116a0dec6b69d305843
kernel: 2.6.32.11-99.fc12.i686.PAE
package: glista-0.4-3.fc12
rating: 4
reason: Process /usr/bin/glista was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 javadieh 2010-05-16 20:55:45 UTC 
Created attachment 414412 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-05-17 12:09:11 UTC 
Thanks for your bug report. Unforunately the backtrace lacks debug symbols. Can you please install them manually with

debuginfo-install glista

and then try reproduce the crash in order do get a full backtrace?
Comment 3 Christoph Wickert 2010-06-05 16:29:52 UTC 
I guess this also is a duplicate of bug 577846, but without a proper backtrace, I cannot be sure.