Comment 16 for bug 539708

I created the log with the file I provided above (org_chromium_ANn03F.pdf).
As stated above, after printing the file (or actually: during the printing),
I get a GUI saying that there was a printing error and that I can diagnose
it (Still, I get a totally black page :-O). Some versions of gs ago, this
popup came before the printing, that saved a lot of ink :-).
*
*
On Thu, Apr 1, 2010 at 10:13, Till Kamppeter <email address hidden>wrote:

> 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/DebuggingPrintingProblems.
>
> If you need your files printed, try to avoid evince. Use Adobe Reader,
> Okular, XPDF, gv, direct printing with "lpr", ... for printing PDF
> files.
>
> --
> /usr/lib/cups/filter/pdftoraster failed
> https://bugs.launchpad.net/bugs/539708
> You received this bug notification because you are a direct subscriber
> of the bug.
>