[cups] Printer not usable from command line, "Filter failed"

[Jarvis Wyatt]

Hi,

> Sent: Tuesday, June 23, 2020 at 1:24 PM
> From: "Helge Blischke" <helgeblischke at web.de>
> To: "The CUPS user discussion list." <cups at cups.org>
> Subject: Re: [cups] Printer not usable from command line, "Filter failed"

[...]

> your log snippets don#t show the document-type of the input file
> nor the filters involved.

It is a simple text file with few lines and only ASCII characters.

> Switch on debug logging (cupsctl —debug-logging), print from the command line
> and then extract all messages containing "[Job xxxx]“ from the error_log.

I performed just two actions in this order:
1) turned on debug logging with `cupsctl --debug-logging';
2) launched again `lpr -P Brother_MFC_L2710DN_series somefile'.
You can find the lines in error_log generated by these two actions here:

https://pastebin.com/cxTZXNTD

I decided to include all the lines, not only those regarding the job,
for completeness. It is a very long log. I hope that you can filter anyway the
lines you find interesting.

> What I see from your snippets is:
> the printer accepts one of these formats:
> –	application/object-stream		(what means raw data)
> –	image/pwg-raster
> –	image/urf
> 
> The filter chain for this printer needs to lead to one of these.

In fact, with `lpr -P Brother_MFC_L2710DN_series' I just successfully managed
to print a pdf file and a png image.
Why instead the simple plain text file isn't accepted? Is there a way to send
it to the printer?
Thank you for your advices.

Wyatt