Bug 573470 - [abrt] crash in xiphos-3.1.2-3.fc13: Process /usr/bin/xiphos was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in xiphos-3.1.2-3.fc13: Process /usr/bin/xiphos was killed by si...
Keywords:
Status: CLOSED DUPLICATE of bug 569685
Alias: None
Product: Fedora
Classification: Fedora
Component: xiphos
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b1c4f4d5630ed2efd8d69ae4ba7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-14 23:08 UTC by Cia Watson
Modified: 2010-03-15 13:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-15 13:21:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (23.09 KB, text/plain)
2010-03-14 23:08 UTC, Cia Watson 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.