Bug#631859: cups: PDF files no longer prints

[Steinar Bang <sb@dod.no>]

>>>>> Brian Potkin <claremont102@gmail.com>:
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Running /usr/bin/pdftops  -level3 -origpagesizes /var/spool/cups/tmp/pdftops.raZCfE -
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Running pstops '1670' 'tlf@DE-BE-20-52-41-53' 'Tilleggsopplysninger.pdf' '1' ' document-name=Tilleggsopplysninger.pdf job-uuid=urn:uuid:3e92a346-37ef-341e-6a2b-64f5b43eff46 job-originating-host-name=10.10.10.10'
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: May not be a PDF file (continuing anyway)
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: PDF file is damaged - attempting to reconstruct xref table...
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: Couldn't find trailer dictionary
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Error: Couldn't read xref table
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Cannot process "<STDIN>": Unknown filetype.
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] Process is dying with "Could not print file <STDIN>
>> D [26/Jun/2011:20:44:41 +0200] [Job 1670] ", exit stat 2

> A problem within the cups filtering system at that time springs to
> mind.  Things have moved since then, so does the issue still occur on
> testing or unstable? Or perhaps the problem disappeared soon after you
> first observed it? Please let us know.

I haven't seen this issue for ages, but if it was fixed or it stopped
appearing because I started using evince to print PDFs instead of
acroread or xpdf, I don't know.

I know that evince was able to print PDFs at a point in time when
acroread and xpdf was failing on the same PDFs.

I also know that the people who have tried printing PDFs on the same
cups printer from windows haven't complained about problems for ages.

So I guess this particular issue is fixed (or at least no longer
reproducable). 

Thanks!


- Steinar