Canon Scanner LiDE 220

Home » CentOS » Canon Scanner LiDE 220
CentOS 7 Comments

Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

This scanner is supported according to the SANE page, but doesn’t work on my up-to-date C7 system (updated 20 minutes ago). The Canon web site is as expected – as useful as a chocolate tea pot.

Has anyone managed to get this to run, and if so can you share the secret please.


7 thoughts on - Canon Scanner LiDE 220

  • For what it’s worth I use a commercial program called VueScan for old/unsupported scanners. I run it on a Mac but it’s also available for Linux and Windows. Might be worth a shot if other avenues don’t pan out.

  • –AChT3FpUh66otGIh7uVGWd6FU1Ke7uTXf Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    Thanks. I’ve downloaded the trial version and it works. If I can’t get SANE to run it at least concerts a brick into something useable.


  • on my C7 system:

    # yum list installed | grep -y sane libsane-hpaio.x86_64 3.13.7-6.el7_2.1 @updates
    sane-backends.x86_64 1.0.24-9.el7 @anaconda
    sane-backends-drivers-scanners.x86_64 1.0.24-9.el7 @anaconda
    sane-backends-libs.x86_64 1.0.24-9.el7 @anaconda

    and my lide 220 works for me. In previous CentOS versions, one had to hack at it because they were shipping old versions of Sane that didn’t have the right incantations done over them. I think that (as one other poster mentioned) it involved downloading Fedora source RPMs and building them, or some such. but I had to do none of that for C7.

  • –0gUUTQg6nDCJnvcgbtRx9wcxtxPA4ptvr Content-Type: text/plain; charset=windows-1252
    Content-Transfer-Encoding: quoted-printable

    # yum list installed | grep -y sane ksaneplugin.x86_64 4.10.5-3.el7 @base libksane.x86_64 4.10.5-3.el7 @anaconda libksane-devel.x86_64 4.10.5-3.el7 @anaconda libsane-hpaio.x86_64 3.13.7-6.el7_2.1 @updates sane-backends.x86_64 1.0.24-9.el7 @base sane-backends-devel.x86_64 1.0.24-9.el7 @base sane-backends-doc.noarch 1.0.24-9.el7 @base sane-backends-drivers-cameras.x86_64
    sane-backends-libs.x86_64 1.0.24-9.el7 @anaconda sane-frontends.x86_64 1.0.14-19.el7 @anaconda xsane.x86_64 0.999-9.el7 @base xsane-common.x86_64 0.999-9.el7 @anaconda xsane-gimp.x86_64 0.999-9.el7 @anaconda
    # sane-find-scanner

    # sane-find-scanner will now attempt to detect your scanner. If the
    # result is different from what you expected, first make sure your
    # scanner is powered up and properly connected to your computer.

    # No SCSI scanners found. If you expected something different, make sure that
    # you have loaded a kernel SCSI driver for your SCSI adapter.

    could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan], chip=GL848+) at libusb:001:005
    # Your USB scanner was (probably) detected. It may or may not be supported by
    # SANE. Try scanimage -L and read the backend’s manpage.

    # Not checking for parallel port scanners.

    # Most Scanners connected to the parallel port or other proprietary ports
    # can’t be detected by this program.

    # xsane
    -> no devices found

    (I know xsane shouldn’t normally be run from root – this was just to eliminate and libusb permission issues.)

    I’ve seen a suggestion that 1.0.26 is required, hence the Fedora suggestion. BTW, I tried a “brute-force” Fedora install, but the dependency hell soon persuaded me of the error of my ways!

    Thanks for your suggestion, Martin


  • Compile the Fedora source rpm on your CentOS system and see what happens. Don’t just blindly install the Fedora binary.

  • Hello,

    On Sat, 2016-08-20 at 18:40 -0400, Fred Smith wrote:

    Support for the LiDE 220 was added in sane-backends-1.0.25. I suppose you are either using a different scanner or made modifications to your installation.

    The original poster probably needs to rebuild using either the C7 SRPM
    with a drop in 1.0.25 tarball (either remove all patches from the spec file or hand pick those still appropriate) or work from a recent Fedora SRPM.

    When building from the C6 SRPM the file /usr/bin/umax_pp has to be added to the SPEC file file list. This might be the case when building from the C7 SRPM also.

    Regards, Leonard.