tags 1013437 - unreproducible thanks
On Sun 03 Jul 2022 at 06:00:28 +0100, Gareth Evans wrote: > On Sat 2 Jul 2022, at 23:43, Brian Potkin <[email protected]> wrote: > [...] > > On Fri 01 Jul 2022 at 13:37:07 +0100, Gareth Evans wrote: > >> Driverless queues don't seem to work > >> no matter how set up. > > > > Yet earlier (and at OpenPrinting) you said: > > > > Having deleted all printers from system-config-printer, > > $ sudo lpadmin -p testq -v ipp://192.168.0.14/ipp/print -E -m > > driverless:ipp://192.168.0.14/ipp/print > > now succeeds, and so does printing to it. > > Apologies, driverless queues only work if set up by lpadmin. > Everywhere queues work from cups-web. OK. That's clear enough. > > May I suggest you may not be able to reproduce the bug as you (said > you) don't have a fax-capable printer? Indeed you may. It had slipped my mind but it was the reason I thought upstream was a reasonable place to go. > It seems to me that my driverless print jobs end up in a fax queue if > the queue is created by cups-web or s-c-p. If this is the main > symptom, I would be grateful if you would advise if this changes what > the bug should be reported against. The PPD generated by everywhere suits queues set up by lpadmin and the CUPS web interface. One of the queues set up with cups-filters, driverless doesn't work. I'd stick with cups-filters for the time being. > I respect that you may no longer wish to be involved with this issue - > thanks for your help - here is some further info for info's sake :) > > At least one other user seems to have a similar problem: > > "However, printing does not work, although the printer gets data, but > then hangs." > https://lists.debian.org/debian-user/2022/06/msg00558.html > > The printer concerned there also appears to have airprint/fax > https://productz.com/en/samsung-xpress-sl-c480fw/p/wxnG7 > > Substituting "gives up" for "hangs", this reflects my issue too. > > I can find no significant difference between driverless PPDs, though > everywhere PPDs do not include fax details, and everywhere queues > added from cups-web succeed in printing. Might this be another > pointer to the issue? You are making a good case. > > $ history | grep testq-drvless > sudo lpadmin -p testq-drvless -v ipp://192.168.0.14/ipp/print -E -m > driverless:ipp://192.168.0.14/ipp/print > > $ sudo cat testq-drvless.ppd | grep -i fax > *NickName: "Brother MFC-L2740DW series, Fax, driverless, cups-filters 1.28.7" > *cupsIPPFaxOut: True > *OpenUI *faxPrefix/Pre-Dial Number: PickOne > *OrderDependency: 10 AnySetup *faxPrefix > *DefaultfaxPrefix: None > *faxPrefix None: "" > *CloseUI: *faxPrefix > *CustomfaxPrefix True: "" > *ParamCustomfaxPrefix Text: 1 string 0 64 > > $ history | grep ippeve > sudo lpadmin -p testq-ippeve -v ipp://192.168.0.14/ipp/print -E -m everywhere > > $ sudo cat testq-ippeve.ppd | grep -i fax > $ > > > Though even testq-drvless sometimes shows strange job attribs in s-c-p: > > "job-printer-state-message: Phone number for fax not valid! Fax cannot be > sent" > "job-printer-uri: ipp://localhost/printers/testq-drvless" > > though the job (from geany) actually printed. > > > $ sudo diff CUPSWEBDL.ppd testq-drvless.ppd > 20c20 > < *APSupplies: "http://mfcl2740dw.local./net/net/airprint.html"; > --- > > *APSupplies: "http://192.168.0.14/net/net/airprint.html"; > > $ sudo diff CUPSWEBDL.ppd SCPDL.ppd > $ > > $ ping mfcl2740dw.local > PING mfcl2740dw.local (192.168.0.14) 56(84) bytes of data. > 64 bytes from 192.168.0.14 (192.168.0.14): icmp_seq=1 ttl=255 time=9.80 ms > > $ ping mfcl2740dw.local. > PING mfcl2740dw.local. (192.168.0.14) 56(84) bytes of data. > 64 bytes from 192.168.0.14 (192.168.0.14): icmp_seq=1 ttl=255 time=3.62 ms > > $ sudo lpadmin -p testqhostname -v ipp://mfcl2740dw.local/ipp/print -E -m > driverless:ipp://mfcl2740dw.local/ipp/print > lpadmin: Printer drivers are deprecated and will stop working in a future > version of CUPS. > > $ sudo diff testqhostname.ppd CUPSWEBDL.ppd > $ > > > $ lp -d testqhostname /etc/nsswitch.conf > request id is testqhostname-56 (1 file(s)) > > Succeeds. Good. > /var/log/cups/error_log > [...] > 2833 D [03/Jul/2022:02:05:45 +0100] Create-Job > ipp://localhost/printers/testqhostname > [...] > 3359 D [03/Jul/2022:02:05:46 +0100] [Client 605] Processing GET > /printers/testqhostname.ppd > 3360 D [03/Jul/2022:02:05:46 +0100] [Client 605] > filename="/etc/cups/ppd/testqhostname.ppd", type=application/vnd.cups-ppd > [...] > 3794 D [03/Jul/2022:02:05:47 +0100] [Job 56] job-uri uri > ipp://mfcl2740dw.local:631/ipp/print/job-225 > 3805 D [03/Jul/2022:02:05:47 +0100] [Job 56] printer-uri uri > ipp://mfcl2740dw.local:631/ipp/print > > > $ lp -d CUPSWEBDL /etc/nsswitch.conf > request id is CUPSWEBDL-55 (1 file(s)) > > Fails. Not good, obviously. > /var/log/cups/error_log > [...] > 70 D [03/Jul/2022:02:04:51 +0100] Create-Job > ipp://localhost/printers/CUPSWEBDL > [from line 1349] > 71 D [03/Jul/2022:02:04:55 +0100] [Client 581] Processing GET > /printers/CUPSWEBDL.ppd > 72 D [03/Jul/2022:02:04:55 +0100] [Client 581] > filename="/etc/cups/ppd/CUPSWEBDL.ppd", type=application/vnd.cups-ppd > [...] > 1495 D [03/Jul/2022:02:04:56 +0100] [Job 55] job-uri uri > ipp://mfcl2740dw.local:631/ipp/faxout/job-224 > 1506 D [03/Jul/2022:02:04:56 +0100] [Job 55] printer-uri uri > ipp://mfcl2740dw.local:631/ipp/faxout You have convinced me that there is something unusual going on here. I haven't any idea why the printer-uri gets to be what it is, but it seems to me to be worth adding to the OpenPrinting report. > lpstat -t shows cups-web created devices as: > > device for CUPSWEBDL: ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/ > > vs > > device for testq-drvless: ipp://192.168.0.14/ipp/print > device for testq-ippeve: ipp://192.168.0.14/ipp/print > > - does the ipp:// string come from Avahi for cups-web created queues? > That's the only place I can find that value: I think so. It is equivalent to ipp://mfcl2740dw.local/ipp/print and ipp://192.168.0.14/ipp/print. > > $ avahi-browse -a > <snip> > + wlp1s0 IPv4 Brother MFC-L2740DW series Web Site > local > + wlp1s0 IPv4 Brother MFC-L2740DW series _scanner._tcp > local > + wlp1s0 IPv4 Brother MFC-L2740DW series Internet Printer > local > + wlp1s0 IPv4 Brother MFC-L2740DW series UNIX Printer > local > + wlp1s0 IPv4 Brother MFC-L2740DW series PDL Printer > local > <snip> > > > Also this error is common: > > $ lpstat -t > scheduler is running > system default destination: SCPDL > device for Brother_MFC_L2740DW_series: > implicitclass://Brother_MFC_L2740DW_series/ > device for CUPSWEBDL: ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/ > <snip> > Brother_MFC_L2740DW_series accepting requests since Mon 27 Jun 2022 22:25:06 > BST > <snip> > printer Brother_MFC_L2740DW_series disabled since Mon 27 Jun 2022 22:25:06 > BST - > No destination host name supplied by cups-browsed for printer > "Brother_MFC_L2740DW_series", is cups-browsed running? > <snip> May we put this on one side for the present? I do not think it is as pressing as the main issue. Thank you for your investigations. Cheers, Brian.
