On Mon 6 Jun 2022, at 14:14, Eduardo M KALINOWSKI <edua...@kalinowski.com.br> wrote: > On 06/06/2022 08:19, Gareth Evans wrote: >> Hello, >> >> I have a strange printing problem which can be replicated on two identical >> printers on two different networks, when printing to wireless driverless IPP >> with Brother MFC-L2740DW printers from Bullseye, whether the printer is >> auto-detected or manually added via ocalhost:631 or system-config-printer. > > I have this exact printer. Driverless printing works, but not with the > automatically generated entry included by cups-browsed (or some other > package), i have to manually add a printer queue using > > # lpinfo -v > > to get a list of URLs (the one starting with ipp:// is the one > necessary), and then something like > > # lpadmin -p Brother2740 -v IPP_URL_FROM_ABOVE -E -m everywhere > >
That worked, and it's now printing normally after reboot via the added profile, thank you Eduardo. Not sure what's happened though as it worked perfectly with both auto-detected and manually-added printer profiles from Bullseye until a week or two ago. My logs suggest no update to system-config-printer. I did change the printer's hostname (on printer console) but both the printer and laptop have been restarted several times since then, printers re-added and re-auto-detected etc. HTTP_STATE_WAITING Closing for error 32 (Broken pipe) - appears in the error log for jobs it is now actually printing, so that seems to be unrelated. I don't like it when things stop working without explanation. Why should adding via the command line work, but not via system-config-printer or localhost:631? Any further debugging tips would be appreciated. Thanks, Gareth > -- > BOFH excuse #201: > > RPC_PMAP_FAILURE > > Eduardo M KALINOWSKI > edua...@kalinowski.com.br