On Thu 21 Dec 2017 at 11:41:01 -0500, Gene Heskett wrote: > On Thursday 21 December 2017 06:51:56 Brian wrote: > > > Considering you have lead the discussion back to your invoice problem > > I'll ask whether the PDF evince produces is viewable, > > Yes, exactly as expected.
Ok, you have just shown that evince produces a decent PDF which looks suitable to send to CUPS. In other words, the blank page you got does not apparently involve anything evince has done. Now send this PDF to CUPS with lp -d <destination_print_queue> <d-file_from_/var/spool/cups> <destination_print_queue> will have to re-enabled with cupsenable <destination_print_queue> Does this print? > > and shows what > > you expect, using what is outlined in > > > > https://lists.debian.org/debian-user/2017/12/msg00584.html > > cupsdisable <destination_print_queue> > > and send the invoice from evince to be printed. Look in /var/spool/cups > for a file beginning with "d" and view it in a PDF viewer. Also use > pdfinfo and pdffonts to compare this PDF and the original one. > > Use cupsenable to revert the first command. > > Its not possible, because a disabled printer is ghosted in the printer > selection menu, yes I do have additional printers, full color and 2% of > the speed of the $110 HL2140. It can do this is 30 seconds including > drum warmup time. The tabloid sized 6920, an mfc, hasn't even sorted out > which paper tray to use in that same 30 seconds. Please see above. Maybe I should have spelled out the full command. > Would I get the same results sending to cups-pdf? No. cups-pdf uses CUPS; CUPS was disabled for the test you did. Its purpose was to determine whether evince was producing a blank PDF. It wasn't. > I can turn that option off on a job by job basis I assume. You mean cupsdisable? You could, but it wouldn't ordinarily be used. -- Brian.
