On Fri, 19 May 2023 16:07:56 +0100 Brian <a...@cityscape.co.uk> wrote:
> On Thu 18 May 2023 at 14:26:13 -0600, Charles Curley wrote: > > [...] > > [...] > > [...] > [...] > > The PDF queue is not part of the printing system. |snarky comment omitted.| > > > Firefox also allows printing from the system printer dialog. When I > > selected that, it showed the same three queues. The two printer > > queues had error messages. > > > > For HP_Laserjet_MFP_m234sdw_C0FB67, "No destination host name > > supplied by cups-browserd for printer "HP_Las..." > > cups-browserd uses mDNS to get the destination host name. OK, it can > come off the rails at times, but ideapc is happy enough with it. > > I'll again mention that neiher cups-browserd nor a manual queue is > required for printing; I gave a test of this in another post. > CUPS should form a temporary queue. I ran "apt purge cups-browsed", then: root@dragon:~# lpstat -l -e HP_LaserJet_MFP_M234sdw_C0FB67 network none ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/ M234ip permanent ipp://localhost/printers/M234ip ipp://192.168.100.134/ipp/print root@dragon:~# lpadmin -x M234ip root@dragon:~# lpadmin -x HP_LaserJet_MFP_M234sdw_C0FB67 root@dragon:~# lpstat -l -e HP_LaserJet_MFP_M234sdw_C0FB67 network none ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/ root@dragon:~# lp /usr/share/cups/data/form_english.pdf lp: Error - No default destination. root@dragon:~# lp -d HP_LaserJet_MFP_M234sdw_C0FB67 /usr/share/cups/data/form_english.pdf request id is HP_LaserJet_MFP_M234sdw_C0FB67-24 (1 file(s)) root@dragon:~# And nothing happened on the printer. I then opened a PDF document in evince, opened the print dialog, and selected that printer. I got a short-lived message, "rejecting jobs". I turned the printer off. The printer went away in the print dialog. I turned it back on. The printer re-appeared, along with the same short-lived "rejecting jobs" message. I went to Netscape. That printed. I begin to think the problem is with GTK's printer dialog. > > > For HP_Laserjet_MFP_m234sdw_C0FB67@hpbm234ethernet.local, I got an > > error message, which disappeared before I could write it down. There > > is now no error message. I tried printing to that, and this time the > > printer came up, showed its "busy" indicator, and did nothing. > > This is often an indication that the dialog is unable to query the > printer. It shouldn't happen on bookworm. > > > > An alternative URI for M234 is > > > > > > ipp://192.168.100.134/ipp/print > > > > > > and the previous lpadmin command could be run with this. It's OK > > > as long as the IP does not change and it also cuts out the moving > > > part of DNS-SD resolution. > > > > That worked: > > > > root@dragon:~# lpadmin -p M234ip -v > > "ipp://192.168.100.134/ipp/print" -E -m everywhere root@dragon:~# > > lp -d M234ip /usr/share/cups/data/form_english.pdf request id is > > M234ip-20 (1 file(s)) root@dragon:~# > > > > It also showed up in Firefox's system printer dialog. I printed to > > it. Nothing. I then printed from Firefox's internal printer > > dialog. That worked. > > The difference between M234 and M234ip is that the latter does not > need to use resolving to get the IP of the ptinter. The queue should > work in Abiword too. I re-installed the M234ip queue. It did not work from abiword. > > > > The problem with the GTK dialog is that it never handled its > > > relationship with CUUPS correctly before bullseye (APIs and all > > > that). However, it *always* got along with manually set up queues, > > > which M234 is. > > > > > > > That isn't what I see here. > > Maybe not, but it is still the case that it was GTK's handling of > printer discovery that was the issue. > > > John Doe seems to think MDNS doesn't like my network > > setup. https://lists.debian.org/debian-user/2023/05/msg00767.html > > I queried hpm234ethernet.localdomain but you seemed happy with it, so > I let it go. > You asked where it came from, and I replied my DHCP and DNS servers. Is there a problem with it? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/