[sane-devel] Epson V600 Perfection Scanner
paddy-hack at member.fsf.org
Mon Jul 23 01:06:56 BST 2018
Monosij Dutta-Roy writes:
> Hi Olaf -
> Thank you for your email and help.
> Attached are the two logs: *sane.debug.127.log.1* and *sane.debug.127.log.2*.
Thanks. From your logs, the epkowa backend is activated courtesy of
/etc/sane.d/dll.d/iscan, not /etc/sane.d/dll.d/epkowa. Looks like I
[dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/iscan
[dll] sane_init/read_config: reading dll.d/iscan
[dll] add_backend: adding backend `epkowa'
When looking for the backend, only the architecture specific directory
is searched but the epkowa backend doesn't live there. It still lives
in /usr/lib/sane, so the iscan-bundle from which you installed has not
been updated for multiarch :-(
[dll] load: searching backend `epkowa' in `/usr/lib/x86_64-linux-gnu/sane'
[dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-epkowa.so.1'
[dll] load: couldn't open `/usr/lib/x86_64-linux-gnu/sane/libsane-epkowa.so.1' (No such file or directory)
[dll] load: couldn't find backend `epkowa' (No such file or directory)
That's something that EPSON will have to fix but in the mean time, you
can work around this for your particular case by one of
- moving the content of /usr/lib/sane to /usr/lib/x86_64-linux-gnu/sane
- adding symbolic links from /usr/lib/x86_64-linux-gnu/sane to files in
- adding /usr/lib/sane to /etc/ld.so.conf
- adding /usr/lib/sane to LD_LIBRARY_PATH in your .profile
i.e. export LD_LIBRARY_PATH=/usr/lib/sane
> On running the second command the Epson scanner was initialized - by the
> sounds generated.
Looks like the device was found by scanimage all right
device `epkowa:interpreter:003:003' is a Epson Perfection V600 Photo flatbed scanner
> However, gscan2pdf still did not 'find' the scanner.
So let's have a look at what
sudo LD_LIBRARY_PATH=/usr/lib/sane SANE_DEBUG_EPKOWA=HEX scanimage > /dev/null 2> log
produces. This tries to scan with the default settings and discards all
the image data. I'm only interested in the log ;-)
> Again, please note this has been happening since Ubuntu 17.10. Until 17.04
> all was fine. I have been clean installing OS and installing scanner
> drivers and then gscan2pdf worked fine.
Distributions keep changing things and it very much looks like the
iscan-bundle is not getting updated to follow suit :-(
> Looking forward to your reply in what may be needed to 'find' the scanner.
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