Bug 800219 - Xiphos crashes at startup after displaying splash screen
Summary: Xiphos crashes at startup after displaying splash screen
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: xiphos
Version: el6
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
: 800221 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2012-03-06 02:36 UTC by fred smith
Modified: 2012-03-28 04:55 UTC (History)
1 user (show)

Fixed In Version: xiphos-3.1.5-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-03-28 04:55:16 UTC
Type: ---

Attachments (Terms of Use)

Description fred smith 2012-03-06 02:36:00 UTC
Description of problem:Running Xiphos from epel on Centos 6.2. has been working for months, but this last week suddenly began crashing at startup, after displaying splash screen.

Version-Release number of selected component (if applicable): 3.1.3-2.el6

How reproducible: always

Steps to Reproduce:
1.start xiphos
Actual results: crash on startup

Expected results: no crash

Additional info: Attaching strace output of the entire session up to the crash.
system is also using the sword library: 1.6.1-1.eo6

Comment 1 Deji Akingunola 2012-03-08 12:19:12 UTC
*** Bug 800221 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Update System 2012-03-08 12:27:45 UTC
xiphos-3.1.5-1.el6 has been submitted as an update for Fedora EPEL 6.

Comment 3 Fedora Update System 2012-03-08 17:25:29 UTC
Package xiphos-3.1.5-1.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing xiphos-3.1.5-1.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-03-28 04:55:16 UTC
xiphos-3.1.5-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.