2 Sep
2023
2 Sep
'23
6:50 p.m.
On Sat, 2 Sep 2023 18:36:42 +0200
Thierry de Coulon via tde-users <users(a)trinitydesktop.org> wrote:
On Saturday 02 September 2023 11.44:43 Dr. Nikolaus
Klepp via tde-users wrote:
[...]
What does your /etc/cups/printers.conf say
DeviceURI dnssd://hp%20LaserJet%204200%20
(0001E6B3586E)._pdl-datastream._tcp.local/
[...]
DeviceURI
dnssd://hp%20LaserJet%204250%20%5B110D32%5D._pdl-datastream._tcp.local/
[...]
DeviceURI
dnssd://Lexmark%20CS310dn._ipp._tcp.local/?uuid=bc2be670-2f17-4299-aeee-4728e21bb0af
These are, however, the files from the working (i-e-
printing) system, with
avahi.
Notice the protocol on those URLs? dnssd = DNS Service Discovery. Which
is what avahi does. Therefore, without avahi, it's no surprise your system can't
find the printers. By contrast, Nikolaus has:
DeviceURI ipp://drucker/printers/MFCJ5320DW
which is a different non-avahi protocol. I have:
DeviceURI socket://192.168.1.104
which again is not avahi-dependent.
Your setup, while not incorrect in the strict sense, is relying on automagic that's
difficult to fix when it breaks.
E. Liddell