Bug 10554

Summary:	Does not recognize a .tif file.
Product:	Mageia	Reporter:	Gary Montalbine <gmontalbine>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	george, pablo
Version:	3
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	leptonica-1.69-2.mga3.src.rpm	CVE:
Status comment:

Description Gary Montalbine 2013-06-18 14:04:00 CEST

I am using M3. I get the following error msg while trying to use tesseract:

[gary@localhost test]$ tesseract savig1.tif savig1
Tesseract Open Source OCR Engine v3.02.02 with Leptonica
Error in findTiffCompression: function not present
Error in pixReadStreamTiff: function not present
Error in pixReadStream: tiff: no pix returned
Error in pixRead: pix not read
Unsupported image type.

The tif works with tesseract in M1.


Reproducible: 

Steps to Reproduce:

Comment 1 George Mitchell 2013-06-18 16:31:33 CEST

I can confirm that tesseract is not working properly.  I used tesseract quite a bit with M2 and now it is quite obviously broken.  I attempted to reuse it on the same tif files that worked perfectly with it before and now I get the exact same error message that Gary is getting.

CC: (none) => george

Comment 2 Pablo Saratxaga 2013-06-18 23:17:50 CEST

same bug as #10403
problem is in wrong libleptonica package, see bug #10411 

updating libleptonica corrects it;

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

Status: NEW => RESOLVED
CC: (none) => pablo
Resolution: (none) => DUPLICATE

Pablo Saratxaga 2013-06-18 23:18:45 CEST

Source RPM: Tesseract => leptonica-1.69-2.mga3.src.rpm

Comment 3 Gary Montalbine 2013-06-18 23:50:33 CEST

I unistalled tesseract and libleptonica. Reinstalled and have the same problem. Where do I get the updated libleptonica?
Gary

Comment 4 George Mitchell 2013-06-19 00:16:26 CEST

Gary,  At this point it has not been released yet.  The version of libleptonica that is included in Cauldren DOES work if you need something right away.  Apparently it will take a few days (or weeks) for a fix for M3 to be released.  When it is, it will appear as an update.