Bug 103270

Summary:	pdftoppm produces blank page for Chase Bank credit card PDF statements
Product:	poppler	Reporter:	Dan Barrett <dbarrett>
Component:	general	Assignee:	poppler-bugs <poppler-bugs>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	medium	CC:	dbarrett, nate
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Screenshot of a PPM file that should be a credit card statement, but is blank A PDF that is converted incorrectly by pdftoppm What "bad.pdf" should look like when converted (screenshot) The bad conversion by pdftoppm of "bad.pdf" What "bad.pdf" looks like after conversion by pdftoppm (screenshot)

Description Dan Barrett 2017-10-14 00:24:41 UTC

Created attachment 134837 [details]
Screenshot of a PPM file that should be a credit card statement, but is blank

Credit card PDF statements from Chase Bank (www.chase.com) display mostly or entirely blank when converted by pdftoppm 0.41.0, which is supplied in Ubuntu 16.04 LTS.

Attached is a screenshot of a typical statement, which should be full of text, but the text is all missing. Sorry I can't include an actual statement due to privacy. But maybe somebody on the dev team has a Chase credit card...?

Adobe Reader and Evince display the statements just fine.

This bug was originally filed against the KDE PDF-display program okular: https://bugs.kde.org/show_bug.cgi?id=385424.  The bug was reproduced there by a developer with a Chase account.

Comment 1 Albert Astals Cid 2017-10-15 21:25:58 UTC

without the actual file it's basically impossible to fix this.

Comment 2 Dan Barrett 2017-10-15 23:29:13 UTC

OK, I used pdftk to isolate the final page of the PDF. pdftoppm still can't display it. I will attach some files:

- bad.pdf: The PDF that pdftoppm displays as mostly blank.
- sorrect-screenshot.jpg: What the display SHOULD look like.

Comment 3 Dan Barrett 2017-10-15 23:30:15 UTC

Created attachment 134851 [details]
A PDF that is converted incorrectly by pdftoppm

Comment 4 Dan Barrett 2017-10-15 23:30:35 UTC

Created attachment 134852 [details]
What "bad.pdf" should look like when converted (screenshot)

Comment 5 Dan Barrett 2017-10-15 23:31:32 UTC

Created attachment 134853 [details]
The bad conversion by pdftoppm of "bad.pdf"

Comment 6 Dan Barrett 2017-10-15 23:32:58 UTC

Created attachment 134854 [details]
What "bad.pdf" looks like after conversion by pdftoppm (screenshot)

Comment 7 Albert Astals Cid 2017-10-16 22:07:43 UTC

You're using an old version of poppler right?

Update to something newer, it works fine for me.

Comment 8 Nate Graham 2017-10-17 03:35:02 UTC

I built poppler from source (git master), installed, and Okular (also git master) still doesn't display the file properly for me. What are you using to view the file, Albert? Or am I holding it wrong?

Comment 9 Nate Graham 2017-10-17 03:37:42 UTC

Never mind, had to reboot first. I too can confirm that it renders correctly with a more recent poppler.

Comment 10 Dan Barrett 2017-10-17 11:24:05 UTC

What is your recommended way to upgrade Poppler in the current Ubuntu LTS (16.04)? Is there (for example) a PPA package you recommend using? Or is the only alternative to rebuild from source (and break package management for poppler on my hosts)? Thanks.

Comment 11 Nate Graham 2017-10-17 13:28:03 UTC

This is more an Ubuntu question, since it's the Ubuntu folks' decision on what versionf of poppler they include in their releases and how much of a lag there is between git master here and what gets shipped there.

Some quick web searching didn't turn up any PPAs that are still maintained. You're probably best off building from source and marking the poppler packages as 'on hold': `sudo apt-mark hold <poppler packages``

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.