I tried to print a very simple PDF containing only two lines of text,
and it did not work. The job is sent to the printer, but it never
prints.
The printer lights blink for a bit, and then the printer goes back to
idle. At first I thought the fault might be with the original PDF or
with
the printing subsystem (CUPS), or even with the printer itself (which
is a Brother DCP-8085DN). But then I printed the PDF from the
command line, and that worked perfectly. So the PDF is fine, and
CUPS is working fine, and so is the printer. That makes me think that
there is something wrong with the data that evince is sending to CUPS.

I have attached two files which I hope will be helpful:
CD_label_CRtheme.pdf is the original PDF.
d00118-001 is the file that CUPS receives from evince. In the CUPS
web interface, I paused the printer, and then printed the file from
evince,
and then retrieved this file d00118-001 from /var/spool/cups

The problem is not limited to this one PDF. I am having the same problem
with other files, but this PDF was particularly small and simple, so I
thought
it would be a good minimal example.

One other bit of information: I also tried printing this file from
evince in a
VM running i386 Debian testing, and that worked just fine. So perhaps
the
bug is not in evince itself, but in one of the libraries it uses?

If there is anything else I can do or any other information I can
provide
to assist in getting to the bottom of this issue, please let me know.

Thank you,
James Dietrich