[sane-devel] Iscan and Ubuntu 17.10/18.04 fixed

Olaf Meeuwissen paddy-hack at member.fsf.org
Sat Nov 18 11:26:02 UTC 2017


Hi,

staedtler-przyborski writes:

> Dear Sane developers,
>
> all Iscan dependend Epson scanners refused to work with Ubuntu 17.10
> (and 18.04)
>
> see https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352.

What a mess.  Changing the package name from libsane to libsane1 and
then expecting nothing breaks???  The Provides: libsane is absolutely
required until all depending packages have been updated to require the
new libsane1 package.

The issue with third party package does not end there.  A lot of them
were created before "multi-arch" so they install in /usr/lib/sane or
/usr/lib64/sane, not in some really architecture dependent place such as
/usr/lib/x86_64-linux-gnu/sane.  There is little change that third party
*vendor* packages will be rebuilt to fix this.

As far as iscan and its interpreters are concerned, to the best of my
knowledge they are no longer actively maintained.  Good luck prodding
EPSON in fixing this.

# Full disclosure: I work at a daughter company of EPSON and have been
# taking care of iscan for over a decade (and spent about five years
# working on utsushi, aka imagescan).

> I know it is not your fault. But maybe some users try to find a solution
> on the sane-devel-mailing- list.

Fortunately not.

> I discovered today a simple fix for this bug (after updating libsane to
> :libsane1 1.0.27-
>
> 1~experimental2ubuntu2.1, curently in proposed).
>
> Copy (or move) the files from /usr/lib/sane (libsane-epkowa.la, libsane-
> epkowa.so.1, libsane-epkowa.so.1.0.15 in my case) to
> /usr/lib/x86_64-linux-gnu/sane

Actually, I'd leave them where they are and create symlinks to them from
where they are expected.  After moving them back to /usr/lib/sane

  cd /usr/lib/x86_64-linux-gnu/sane
  ln -s ../../sane/libsane-epkowa.la
  ln -s ../../sane/libsane-epkowa.so.1
  ln -s ../../sane/libsane-epkowa.so.1.0.15

> after a reboot the Iscan dependend scanners (verified with a Epson V300)
> start to work.

You shouldn't have to reboot.  Just restart your application.

> Maybe Epson delivers updated packages some day so the manual correction
> will be unnecessary

Like I said, good luck with that.

Hope this helps
--
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join



More information about the sane-devel mailing list