Ernst, I have tried it out by printing it into a PDF file with evince first (to get an Evince-rerendered version) and try to render that one directly with Ghostscript. Ghostscript errors out before sending the first pixel of the CUPS Raster output to the driver. So probably the driver interprets the missing input data as black pixels instead of erroring out by itself.
Ernst, I have tried it out by printing it into a PDF file with evince first (to get an Evince-rerendered version) and try to render that one directly with Ghostscript. Ghostscript errors out before sending the first pixel of the CUPS Raster output to the driver. So probably the driver interprets the missing input data as black pixels instead of erroring out by itself.
Can you please provide an error_log as described in the "CUPS error_log" section of https:/ /wiki.ubuntu. com/DebuggingPr intingProblems.
If you need your files printed, try to avoid evince. Use Adobe Reader, Okular, XPDF, gv, direct printing with "lpr", ... for printing PDF files.