Am Mon, 15 Feb 2021 15:12:49 +0000 schrieb Brian Potkin <claremont...@gmail.com>:
> On Mon 15 Feb 2021 at 14:27:59 +0100, mh wrote: > > > Am Mon, 15 Feb 2021 10:26:52 +0000 > > schrieb Brian Potkin <claremont...@gmail.com>: > > > > > On Sun 14 Feb 2021 at 20:31:28 +0100, mh wrote: > > > > > > [...] > > > > > > > # ippfind -T 5 > > > > ~# > > > > > > An IPP printer is not found. This would fit the observation that > > > cups-browsed has not set up a print queue. I have come to the > > > conclusion that the B432 does not implement IPP-over-USB > > > correctly. > > > > First: Thanks for your help and for all your efforts. But further > > investigation and tests based on the new knowledge provided by you > > lets me come to a different conclusion (see below). I didn't know > > about ipp-usb, how it works and what it does and it automagically > > being configured. > > I've tried to help with understanding by quoting a wiki link. Yes. Thanks for that. I only wanted to point out I wasn't aware of what actually happens during cups config. I have a better understanding. > > > > A queue set up with a vendor PPD will not function while ipp-usb > > > is active, Only for curiosity: On systems where there is NO problem, why do I see one printer in cups config (network printer) resulting in two printers in the printing menu? > so purge it and proceed as you did with the Live ISO. > > > Also see #982190: > > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982190 > > > > > > Cheers, > > > > > > Brian. > > > > Purging ipp-usb instantly made the cups webinterface showing my > > printer. So I could configure it using the vendor PPD file. Printing > > menue (Libreoffice) shows one OKI printer. Print succeeded. > > Thanks. > > The printer would have shown under Local Printers. With ipp-usb > active it shows under Discovered Network Printers. This is because > IPP-over-USB effectively treats the printer as a network connected > device, not a USB connected device. > > https://wiki.debian.org/SystemPrinting#The_CUPS_Web_Interface > > > So the main issue is solved as I can print from within my > > default system. From what I've seen during configuration and > > printing, the printer setup seems stabel, the printer showed up > > immediately, the print job is carried out without much delay. > > Good. > ... > > > I then investigated the LIVE-ISO. To my surprise ipp-usb is > > installed within the LIVE-ISO. All the commands which failed/did > > have an empty output on my default system work here with the > > expected output (I guess), except for # avahi-browse -rt _ipp._tcp > > due to avahi-browse not being installed: > > This is the concerning part. Why do some commands like ippfind, > lpstat -e and avahi-browse give empty outputs on Debian unstable? Are > the Debian and Live ISO versions of ipp-usb the same? It is all Debian/unstable. And it does not depend on the version of ipp-usb ( 0.9.16-1 and 0.9.17-1 ). Both work on live-iso (from 2021.02, the 2020.07 version didn't ship ipp-usb ) or new installation (2021.02 dist-upgraded), neither work with my old installation. I know this for a fact because the problem persist longer than 0.9.17-1 exists. I can live without ipp-usb working on this installation. But if someone tells me how to investigate the flaw, I am happy to investigate, too. > ... > You would submit a wishlist bug against printer-driver-oki. I will. > > Thank you for your detailed report. > > Brian. Thank you for all your help. Michael
