Bug 670032

Summary: [abrt] sword-1.6.2-1.fc15: Process /usr/bin/osis2mod was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Matěj Cepl <mcepl>
Component: swordAssignee: Deji Akingunola <dakingun>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 19CC: dakingun, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1bdbae685d7b2668ff5b1b46fe248e5beb709bc0
Fixed In Version: bibletime-2.10.0-1.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-14 07:50:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Matěj Cepl 2011-01-16 20:19:40 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: osis2mod /home/matej/.sword/modules/texts/ztext/czekms -
component: sword
executable: /usr/bin/osis2mod
kernel: 2.6.37-2.fc15.x86_64
package: sword-1.6.2-1.fc15
reason: Process /usr/bin/osis2mod was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1295208677
uid: 500

How to reproduce
-----
1.have valid OSIS file (http://mcepl.fedorapeople.org/tmp/bible.xml.bz2)
2. run cat bible.xml |osis2mod ~/.sword/modules/texts/ztext/czekms -
3. observe crash

Comment 1 Matěj Cepl 2011-01-16 20:19:49 UTC
Created attachment 473734 [details]
File: backtrace

Comment 2 Fedora End Of Life 2013-04-03 18:31:15 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Fedora Update System 2014-01-30 01:25:26 UTC
bibletime-2.10.0-1.fc20,xiphos-3.1.6-1.fc20,sword-1.7.2-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/bibletime-2.10.0-1.fc20,xiphos-3.1.6-1.fc20,sword-1.7.2-1.fc20

Comment 4 Fedora Update System 2014-01-31 04:27:18 UTC
Package bibletime-2.10.0-1.fc20, xiphos-3.1.6-1.fc20, sword-1.7.2-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bibletime-2.10.0-1.fc20 xiphos-3.1.6-1.fc20 sword-1.7.2-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-1836/bibletime-2.10.0-1.fc20,xiphos-3.1.6-1.fc20,sword-1.7.2-1.fc20
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2014-02-14 07:50:35 UTC
bibletime-2.10.0-1.fc20, xiphos-3.1.6-1.fc20, sword-1.7.2-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.