On Mon 27 Jun 2022 at 18:43:16 +0100, Gareth Evans wrote: > On Mon 27 Jun 2022, at 18:41, Till Kamppeter <till.kamppe...@gmail.com> wrote: > [...] > > Seems that it is able to access the printer for sending a job to it > > (done as user "lp"?) but not to poll the printer's capabilities via IPP > > (when running the "lpadmin" command). > > The printer/queue was not created, so I didn't get as far as testing printing. > > Which is to say that testqq didn't appear in system-config-printer.
ipp://192.168.0.14/ipp/print is the most fundamental URI available. Assuming the IP address is unchanged, do (as root) cupsctl --debug-logging >/var/lod/error_log Set up a driverless queue as before. Compress error_log with gz or xz and send it here. Cheers, Brian.
