Bug 32065

Summary:	Poppler 0.15.x won't open file but poppler 0.14.x and xpdf can open it.
Product:	poppler	Reporter:	npscott
Component:	general	Assignee:	poppler-bugs <poppler-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description npscott 2010-12-02 16:01:40 UTC

In evince a certain pdf url was said to be corrupt in 0.15.3

The same file opened flawlessly in 0.14.5.  Xpdf reads the pdf flawlessly as well.

The same results happened with epdfview and okular ( both depend on poppler ) so  it seems to be a poppler 0.15.x problem.

here is the offending url

http://www.skatecanada.ca/en/athletes/national_teams/international_assignments/2010-2011-Selection-Criteria.pdf

Comment 1 Albert Astals Cid 2010-12-03 00:52:44 UTC

Works for me. Are you sure you have rebuilt your programs using poppler since there were changes in poppler that might need that?

Comment 2 npscott 2010-12-03 21:02:58 UTC

Yes I did rebuild evince to test after building poppler 0.15.3.

I also did the same with epdfview and okular.

All of them yield the same results.  This is the only stubborn PDF file I have come across so far.

Comment 3 npscott 2010-12-03 22:06:50 UTC

Here is the command line error messages I get with evince and epdfview.

Error: Internal: called getRawChars() on non-predictor stream
Error: PDF file is damaged - attempting to reconstruct xref table...
Error: Couldn't find trailer dictionary
Error: Couldn't read xref table

Comment 4 Albert Astals Cid 2010-12-04 03:23:10 UTC

Can you please paste your configure/cmake output? Specially the summary at the end.

Comment 5 npscott 2010-12-04 19:39:57 UTC

Problem fixed.

I originally passed the --enable-zlib ( which worked in the 0.14.x serides ) when I compiled it.

Recompiling the code without the --enable-zlib fixed the problems.

Comment 6 Albert Astals Cid 2010-12-05 04:07:55 UTC

Will be fixed for poppler 0.16.0

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.