Created attachment 364102 [details] emerge --info app-text/qpdfview-0.4.[3,6] doesn't print any text nor graphics, only table outlines and background patterns are visible. This happens on a PDF whose info are: Producer: iText 2.0.8 (by lowagie.com) CreationDate: Wed Nov 27 20:56:02 2013 ModDate: Wed Nov 27 20:56:02 2013 Tagged: no Form: none Pages: 1 Encrypted: no Page size: 595.28 x 841.88 pts (A4) Page rot: 0 File size: 13345 bytes Optimized: no PDF version: 1.4 CUPS reports no error. Printer: Epson Stylus SX620FW, Driver: Generic Epson (ESC/P-R) for Linux v1.1.1 The same file is printed correctly by Acroread. I can provide it via private email (privacy concerns).
Try the following: 1) pdf2ps your.pdf 2) pdftops your.pdf open the resulting .ps files with qpdfview and try to print them (needs qpdfview to be built with USE="postscript") If 1) works to print but not 2) we have the same issue ;) I googled for it already once, and it looks like a bug in PSOutputDev (poppler issue).
(In reply to Franz Fellner from comment #1) > Try the following: > 1) pdf2ps your.pdf got errors: **** Error reading a content stream. The page may be incomplete. **** File did not complete the page properly and may be damaged. **** Warning: File has unbalanced q/Q operators (too many q's) **** This file had errors that were repaired or ignored. **** The file was produced by: **** >>>> iText 2.0.8 (by lowagie.com) <<<< **** Please notify the author of the software that produced this **** file that it does not conform to Adobe's published PDF **** specification the result looks exactly the same as the broken print out. > 2) pdftops your.pdf no error, but the resulting ps is broken -- can't even open it. > open the resulting .ps files with qpdfview and try to print them (needs > qpdfview to be built with USE="postscript") > > If 1) works to print but not 2) we have the same issue ;) > I googled for it already once, and it looks like a bug in PSOutputDev > (poppler issue). So, it doesn't look the same issue. Clearly my PDF file is (partially) broken, but I didn't make it myself -- I wonder if I should file a bug for itext which is the software used to make it... However if Acroread can handle it, still poppler might by at fault here.
(In reply to sphakka from comment #2) > So, it doesn't look the same issue. Clearly my PDF file is (partially) > broken, but I didn't make it myself -- I wonder if I should file a bug for > itext which is the software used to make it... However if Acroread can > handle it, still poppler might by at fault here. Any chance you could try with some other poppler-based viewer such as okular?
(In reply to Davide Pesavento from comment #3) > Any chance you could try with some other poppler-based viewer such as okular? ping?
(In reply to Davide Pesavento from comment #4) > (In reply to Davide Pesavento from comment #3) > > Any chance you could try with some other poppler-based viewer such as okular? > > ping? Okular? No thanks: I spent ages sanitizing my system from most KDE-related stuff ;-) Is there any other reader I can try? Else I can send you the failing PDF file.
(In reply to sphakka from comment #5) > Okular? No thanks: I spent ages sanitizing my system from most KDE-related > stuff ;-) Is there any other reader I can try? Else I can send you the > failing PDF file. Fair enough. Email me the file please.
The reporter sent me the troublesome file some time ago (sorry for the delay, I was traveling). I tried both pdf2ps and pdftops, neither gave any errors during the conversion. Okular (4.11.? w/ poppler-0.24.{3,5}) had no problems opening the resulting postscript files, and they were displayed just fine AFAICT. I don't have access to a printer right now, but will try asap. Which version of poppler are you on?
Please report back if this still fails with latest poppler and qpdfview.
It works (~qpdfview-0.4.14 & related deps)!
