tags 950690 upstream thanks
On Tue 04 Feb 2020 at 21:42:03 +0100, Yves-Alexis Perez wrote: > Package: cups-filters > Version: 1.27.0-2 > Severity: important > > Hi, > > since “some” time (few weeks maybe, I guess the 1.27.0 upload), I can't > print on my Brother HL-5250DN network printer (which was working just > fine earlier). > > The printer is laser monochrome, and I always was able to print color > and monochrome stuff, conversion was happening just fine. > > Now, when I try to print, nothing happens and I guess an error in the > logs about: > > W [04/Feb/2020:21:28:45 +0100] [Job 570] Grayscale/monochrome printing > requested for this job but Poppler is not able to convert to > grayscale/monochrome PostScript. > W [04/Feb/2020:21:28:45 +0100] [Job 570] Use \"pdftops-renderer\" option > (see README file) to use Ghostscript or MuPDF for the PDF -> PostScript > conversion. > > First, it's really not obvious from the log *which* README this is > about, and I had to dig a little before finding it was the one from > cups-filters. > > Then, I tried to set pdftops-renderer-default to various options (gs, > pdftocairo) using: > > lpadmin -p printer -o pdftops-renderer-default=<foo> > > but it didn't work. > > With: > > - gs: nothing prints, but nothing happens in the logs > - pdftocairo: same error message than without any option > - pdftops: same error > > With mupdf it does send something to the printer but the results shows: > > ERROR NAME; > undefined > COMMAND; > ° > OPERAND STACK; > > and in the logs I get: > > W [04/Feb/2020:21:34:29 +0100] [Job 573] Level 3 PostScript not > supported by mutool. > > Downgrading to 1.26.2 from testing seems to fix the problem (I still > have the log entry, though, it seems, so maybe it's unrelated). Thank you for your report, Yves-Alexis. Your issue seems connected with https://github.com/OpenPrinting/cups-filters/issues/169 and its associated bugs. I take it you are using the PostScript PPD provided by Brother. I did test how filtering went with it and a file or two. I got no errors, but did get the warnings you got. Then again, I do not have the printer to print the output file to. I am not sure I really understand all that is involved here, so, because you are able to provide first-hand experience, suggest you forward the issue upstream. Regards, Brian.
