[cups] ippeveprinter - how to set up with real printer?

[Kurt Pfeifle]

Am Di., 8. Okt. 2019 um 16:18 Uhr schrieb Zdenek Dohnal zdohnal at redhat.com
<http://mailto:zdohnal@redhat.com>:


> I'm trying to test ippeveprinter printer application which comes with
> CUPS-2.3.0:
>
> # ippeveprinter -D socket://<printer-ipv4-addr>:9100 -c
> /usr/lib/cups/command/ippeveps -P /etc/cups/ppd/BRQ-TPBC-1D124-North.ppd
> -d /var/spool/cups brno4-tpbc-1st-north -v
>
Why do you connect an *IPP Everywhere* printer to a *socket://* backend?
Any reason which I’m not aware of?

Isn’t it more logical to try something like:

  ippeveprinter -D ipp://<printer-ipv4-addr>/ipp/print \
    -c /usr/lib/cups/command/ippeveps \
    -P /etc/cups/ppd/BRQ-TPBC-1D124-North.ppd \
    -d /var/spool/cups brno4-tpbc-1st-north \
    -v

?

then I can see the print queue in print dialog, but then print dialog
> (in evince, in this case) gets stuck on "Getting printer attributes".
>
There is no IPP language spoken via *socket://*, hence no IPP printer
attributes can be retrieved?

It may well be that I’m completely off…
<https://lists.cups.org/mailman/listinfo/cups>

Cheers,
Kurt