Comment 19 for bug 1871011

      Why not just distribute the working version? The problem with snaps
is they screw the functionality of shared libraries wasting memory.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
    Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Wed, 5 Jan 2022, Till Kamppeter wrote:

> Date: Wed, 05 Jan 2022 22:31:56 -0000
> From: Till Kamppeter <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1871011] Re: USB scanning and printing broken on focal by
> ippusbxd (was: hpmud and ippusbxd conflict)
>
> As ippusbxd by itself is broken, meaning that it even does not work very
> well with the devices it is actually designed for, I am also in favor of
> removing it from all still supported Ubuntu versions (especially LTS).
> Then it does not block devices which could otherwise work better.
>
> To the users whose device needed ippusbxd we should tell to install the
> ipp-usb Snap then, at it does the task of supporting IPP-over-USB
> devices correctly and to their full extent.
>
> ipp-usb Snap:
>
> https://snapcraft.io/ipp-usb
>
> ippusbxd replacement by ipp-usb:
>
> https://github.com/OpenPrinting/ippusbxd#before-you-begin-ippusbxd-or-
> ipp-usb
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1873748).
> https://bugs.launchpad.net/bugs/1871011
>
> Title:
> USB scanning and printing broken on focal by ippusbxd (was: hpmud and
> ippusbxd conflict)
>
> Status in HPLIP:
> Invalid
> Status in hplip package in Ubuntu:
> Expired
> Status in ippusbxd package in Ubuntu:
> Confirmed
>
> Bug description:
> SOLUTION : sudo apt remove ippusbxd
>
> ---- Initial report -----
>
> On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3.
>
> Previously there was a libmtp (udev) bug erroneously detecting HP
> printers as mtp devices. This was fixed. Now, I can try to scan-- from
> both simple-scan and hp-scan, hplip errors out:
>
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0
> Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy
>
> Printer/scanner is an Officejet 4635. Scanning previously worked just
> fine a few months ago. Regression?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions
>