Bug 15629

Summary:	JPX images in PDFs are not displayed
Product:	poppler	Reporter:	Pedro Villavicencio <pvillavi>
Component:	general	Assignee:	poppler-bugs <poppler-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	CanOfSpam3, hank
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Pedro Villavicencio 2008-04-21 07:53:50 UTC

This report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/poppler/+bug/219361

"Download a PDF from Google Book Search (say, from http://books.google.com/books?id=jpceAAAAMAAJ ). Open it with evince. Something like the following will be output on the console:

Error (88087): 12697 extraneous bytes after segment
Error (97507): Error in JPX stream
Error (88087): 12697 extraneous bytes after segment
Error (97507): Error in JPX stream
Error (86590): 12697 extraneous bytes after segment
Error (86590): 12697 extraneous bytes after segment
Error (87420): 12697 extraneous bytes after segment
Error (87420): 12697 extraneous bytes after segment
Error (98085): 12697 extraneous bytes after segment
Error (98085): 12697 extraneous bytes after segment
Error (99312): 12697 extraneous bytes after segment
Error (106918): Error in JPX stream
Error (99312): 12697 extraneous bytes after segment
Error (106918): Error in JPX stream

GhostScript and Acroread both display the embedded images properly."

poppler version: 0.6.4-1

PDF: http://launchpadlibrarian.net/13579707/N9Y4AAAAMAAJ.pdf

Thanks,

Comment 1 Albert Astals Cid 2008-06-13 16:04:51 UTC

Will be fixed with next poppler major release 0.10 if your distribution builds poppler using openjpeg

Comment 2 Hank Bromley 2009-03-19 11:26:16 UTC

Thanks much for this fix, which has corrected a significant problem we were having at the Internet Archive with pdfs that had been created by Google.

One followup question:

With poppler 0.10.4 built against OpenJPEG, the images render correctly, and the "Error in JPX stream" errors go away, but we do still get the "<n> extraneous bytes after segment" errors. Does anyone know what those are about? Should we be concerned about them, or can we safely ignore them?

Comment 3 Albert Astals Cid 2009-03-19 11:54:47 UTC

The message means the stream seems to have some garbage at the end, it's a message to say we are ignoring them, if you see the pdf correctly it's nothing to worry about.

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.