Bug 759508

Summary: [abrt] cuneiform-1.1.0-4.fc14: next_symb: Process /usr/bin/cuneiform was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Yaric <yaricp>
Component: cuneiformAssignee: Dmitrij S. Kryzhevich <kryzhev>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: kryzhev
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:34faf64f30ce436a3daa2c85ccd2b1e5d32174a0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 13:54:47 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
example file for recognition none

Description Yaric 2011-12-02 14:58:41 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 44681 bytes
cmdline: cuneiform -l ruseng -f text -o /home/music/.yagf/output.txt /home/music/.yagf/input.bmp
component: cuneiform
Attached file: coredump, 52027392 bytes
crash_function: next_symb
executable: /usr/bin/cuneiform
kernel: 2.6.35.14-103.fc14.i686
package: cuneiform-1.1.0-4.fc14
rating: 4
reason: Process /usr/bin/cuneiform was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1322827619
uid: 500

How to reproduce
-----
1.scan
2.
3.

Comment 1 Yaric 2011-12-02 14:59:01 UTC
Created attachment 539678 [details]
File: backtrace

Comment 2 Dmitrij S. Kryzhevich 2011-12-05 02:30:51 UTC
////
$ cuneiform -l ruseng -o 0001.tiff.txt 0001.tiff 
Cuneiform for Linux 1.1.0

bash-4.2$ rpm -q cuneiform
cuneiform-1.1.0-4.fc16.x86_64
////

Not reproduced with single step "scan". Could you provide that your file? Or any other craching cuneiform?

Comment 3 Yaric 2011-12-05 04:58:26 UTC
I m sorry!

I began to recognition more then 100 pages.
And saw message about error in cuneiform near 5 minutes after start.
Result of recognition turned out not correct.

Comment 4 Dmitrij S. Kryzhevich 2011-12-06 02:51:06 UTC
So again. Could you provide file that crash cuneiform? If you saw crash report it means it crashed obviously.

If you cant, sorry, but I'l have to close this bug report with "notabug" resolution.

Comment 5 Yaric 2011-12-06 17:40:59 UTC
Created attachment 541490 [details]
example file for recognition

several of this kind files make crash cuneiform

Comment 6 Dmitrij S. Kryzhevich 2011-12-22 05:41:31 UTC
Had tried for namy variants of keys. Can't reproduce. All I get:
$ cuneiform -l ruseng -f text -o 2_1L.tif.txt 2_1L.tif
Cuneiform for Linux 1.1.0

And output 2_1L.tif.txt contain recognized text. Any other example?

Comment 7 Dmitrij S. Kryzhevich 2011-12-22 05:42:39 UTC
Need to add. I have F16 on my machine. May be it somehow influence.

Comment 8 Fedora End Of Life 2012-08-16 13:54:49 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping