[Printing-architecture] 'driverless' doesn't find CUPS shared print queues - expected or a bug?
zdohnal at redhat.com
Mon Jun 7 06:29:31 UTC 2021
I have an bug which I can reproduce in my LAN
(https://bugzilla.redhat.com/show_bug.cgi?id=1954469) and in that bug
Solomon reported a problem which he has with driverless in his setup.
He uses client and server topology in his LAN where server shares print
queues in LAN, and 'driverless' on the client machine doesn't return any
uris, but ippfind and avahi-browse can see the queues.
Is it an expected behavior or a bug?
AFAIK 'driverless' has never returned remote print queues in the past,
and driverless sets '! --txt printer-type' to exclude remote print
queues during generating ippfind arguments, so IMO it is the expected
behavior. IIUC driverless was introduced to have a way how to install
driverless print queue for a printer in cases when GUI isn't able to
work with temp queues. And remote CUPS queues were intended to be
covered via cups-browsed, so that can be the reason (together with the
reason that they aren't real devices) why driverless doesn't report them.
I'm writing this to verify my findings and my understanding of the code
with you as the original author, so I will not mystify other people in
Thank you in advance and have a nice day,
Red Hat Czech - Brno TPB-C
More information about the Printing-architecture