Bug#1013437: cups: Nothing prints from driverless IPP queues unless added via lpadmin

[Brian Potkin <claremont102@gmail.com>]

On Mon 27 Jun 2022 at 17:22:22 +0100, Gareth Evans wrote:

> On Mon 27 Jun 2022, at 17:11, Till Kamppeter <till.kamppeter@gmail.com> wrote:
> > And are you able to print now?
> >
> >     Till
> >
> 
> Only to the queue added via lpadmin ... everywhere
> 
> No autodetected printers appear in system-config-printer or application print dialogs.
> 
> $ sudo lpadmin -p testq -v "ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local" -E -m driverless:"ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local"
> [sudo] password for user: 
> lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS.
> 
> $ lp -d testq /etc/nsswitch.conf
> request id is testq-12 (1 file(s))
> 
> Nothing prints over 5GHz, nor 2.5GHz wifi connections.
> 
> Same behaviour as before in both cases - printer lights up but nothing prints.

The problem I have here is in understanding. A queue set up with the
cups-filters driverless for -m is based strongly on CUPS everywhere.

Here is a URI for the device. It is equivalent to what you already
have:

  ipp://192.168.0.14/ipp/print

Set up

  lpadmin -p testeveq -v ipp://192.168.0.14/ipp/print -E -m everywhere

and print to testeveq as before. We expect this to work.

Now

  lpadmin -p testq -v ipp://192.168.0.14/ipp/print -E -m driverless:ipp://192.168.0.14/ipp/print

and print to testq. How does that go?

Cheers,

Brian.