I am assuming the advice here will be revamped. Therefore, I have a suggestion to be considered for inclusion. But first a quote from Michael Sweet, the creator and principal maintainer of CUPS (substitute ipp-usb for ippusbxd :
Basically, this is an AirPrint printer that supports IPP-USB. When connected, ippusbxd claims the endpoints used for IPP-USB, which happen to also be the endpoints needed for legacy USB printing. Therefore, the USB backend can see it but not access (claim) it.
Basically, vendor scanner and printing drivers will not work when ipp-usb is active. This is a hardware issue and nothing can be done to alter it, although its impact can be lessened via software,
Any non-working print or scanner entry is likely to be noticed by some users. Many will ignore it (driverless printing and scanning will still work), others might be concerned. My suggestion is to point out this situation in the previous mentioned documentation, emphasising that it really isn't a problem.
I am assuming the advice here will be revamped. Therefore, I have a suggestion to be considered for inclusion. But first a quote from Michael Sweet, the creator and principal maintainer of CUPS (substitute ipp-usb for ippusbxd :
Basically, vendor scanner and printing drivers will not work when ipp-usb is active. This is a hardware issue and nothing can be done to alter it, although its impact can be lessened via software,
Any non-working print or scanner entry is likely to be noticed by some users. Many will ignore it (driverless printing and scanning will still work), others might be concerned. My suggestion is to point out this situation in the previous mentioned documentation, emphasising that it really isn't a problem.
-- Brian_p.