JPX images in PDFs are not displayed

Bug #219361 reported by Adam Buchbinder
2
Affects Status Importance Assigned to Milestone
Poppler
Fix Released
Medium
poppler (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

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

The errors continually display, and embedded JPX images (such as the frontispiece of the above-linked book) do not display. The same results are evident when I use pdfimages, implying that the problem is not with evince, but with poppler.

GhostScript and Acroread both display the embedded images properly.

I am using libpoppler2 0.6.4-1~gutsy1 on Gutsy.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, Which book? can you attach one to the report?

Changed in poppler:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Adam Buchbinder (adam-buchbinder) wrote :

It works for any book which has some JPX-encoded images in it. I linked to one above, but I'll attach one to the bug report if that helps. It's the smallest affected PDF I could find.

Changed in poppler:
status: Incomplete → New
Revision history for this message
In , Pedro Villavicencio (pedro) wrote :

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,

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Confirmed on hardy, will look upstream. thanks you.

Changed in poppler:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugs.freedesktop.org/show_bug.cgi?id=15629

Changed in poppler:
status: Confirmed → Triaged
Changed in poppler:
status: Unknown → Confirmed
Revision history for this message
In , Albert Astals Cid (aacid) wrote :

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

Changed in poppler:
status: Confirmed → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

that's fixed upstream now, thanks for reporting!

Changed in poppler:
status: Triaged → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the new version has been uploaded to jaunty now

Changed in poppler:
status: Fix Committed → Fix Released
Revision history for this message
In , Hank Bromley (hank-archive) wrote :

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?

Revision history for this message
In , Albert Astals Cid (aacid) wrote :

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.

Changed in poppler:
importance: Unknown → Medium
Changed in poppler:
importance: Medium → Unknown
Changed in poppler:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.