I have a PDF file on Fedora 39 that, although handed to the print driver, just disappears from the print queue. I suppose that rasterization fails. If I understand correctly, this is done by ghostscript. Where do I start with debugging this?
Is that that only this specific pdf file that doesn’t print? And does printing pdf files usually work?. Does the file open properly using a pdf viewer for example evince
?
You are right, I should just try manually.
Even the preview at researchgate is faulty:
okular:
no problem (apparently)
evince:
says some font thing failed but shows something
Looking at the output, there seems to be no glyph for “greek uppercase lambda” and other elements.
gs
Says:
Page 1
Loading font Times-Roman (or substitute) from
/usr/share/ghostscript/Resource/Font/NimbusRoman-Regular
Loading font Times-Italic (or substitute) from
/usr/share/ghostscript/Resource/Font/NimbusRoman-Italic
Loading font Times-Bold (or substitute) from
/usr/share/ghostscript/Resource/Font/NimbusRoman-Bold
Page 2
Loading font Courier (or substitute) from
/usr/share/ghostscript/Resource/Font/NimbusMonoPS-Regular
Loading font Symbol (or substitute) from
/usr/share/ghostscript/Resource/Font/StandardSymbolsPS
Page 3
**** Warning: cannot process embedded stream for font object 25 0
**** Attempting to load a substitute font.
Loading font JBJPBA+MathematicalPi-Three (or substitute) from
/usr/share/ghostscript/Resource/Font/NimbusRoman-Regular
**** Error: Page drawing error occurred.
Output may be incorrect.
Page 6
**** Error: Page drawing error occurred.
Output may be incorrect.
Page 7
**** Error: Page drawing error occurred.
Output may be incorrect.
The following errors were encountered at least once while processing this file:
error executing PDF token
error reading a stream
The following warnings were encountered at least once while processing this file:
A page ended after a BT had been executed and without a mtching ET
**** This file had errors that were repaired or ignored.
**** The file was produced by:
**** >>>> Acrobat Distiller 2.0 for Power Macintosh; modified using iText 4.2.0 by 1T3XT <<<<
**** Please notify the author of the software that produced this
**** file that it does not conform to Adobe's published PDF
**** specification.
I reckon the printer subsystem is right rejecting faulty input then. However, is there anywhere a logfile of its work? I found nothing in the log for facility lpr
.
It may be possible to fix that quickly and easily.
I have had similar issues with printing some PDFs and the fix that worked for me was to open the pdf using masterPDFeditor and save it with a different name. The newly saved file printed properly.
Very interesting. I had masterPDFeditor bookmarked, but I don’t remember doing it–must have been a long time ago. Seems like an outstanding utility.
Was there any root cause determined for this?
How was this finally resolved, @veteranporter ? masterPDFeditor?
masterPDFeditor has switched to a 30 day free trial then quits working unless it has been registered. I seem to recall that it previously allowed use for some longer time without registering
For me any pdf opened and saved by that app prints, even though the original may not print.