Bug 573470

Summary: [abrt] crash in xiphos-3.1.2-3.fc13: Process /usr/bin/xiphos was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Cia Watson <cia.watson>
Component: xiphosAssignee: Deji Akingunola <dakingun>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dakingun
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:b1c4f4d5630ed2efd8d69ae4ba7f49cda78fce17
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-15 13:21:43 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 Cia Watson 2010-03-14 23:08:21 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: xiphos
comment: Since Xiphos was updated I wanted to see if it would connect / launch without crashing. It didn't.
component: xiphos
executable: /usr/bin/xiphos
kernel: 2.6.33-1.fc13.i686.PAE
package: xiphos-3.1.2-3.fc13
rating: 4
reason: Process /usr/bin/xiphos was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Rawhide)

How to reproduce
-----
1. Click connect after initial launch of Xiphos at module manager
2.
3.
Comment 1 Cia Watson 2010-03-14 23:08:23 UTC 
Created attachment 400064 [details]
File: backtrace
Comment 2 Deji Akingunola 2010-03-15 13:21:43 UTC 
Thanks for testing again, the issue is being tracked upstream. Since this is the same bug as the one you reported earlier, I'm closing this as a duplicate of the other.

*** This bug has been marked as a duplicate of bug 569685 ***