[sane-devel] Fw: Re: Configuring OCR tool [SOLVED]

Olaf Meeuwissen paddy-hack at member.fsf.org
Tue Aug 6 12:34:37 BST 2019


Business Kid writes:

>>Now, the scanner end has sat down. Hmmph! scanimage -L reports:
> scanimage -L
>>device `hpaio:/net/hp_laserjet_mfp_m129-m134?ip=' is a Hewlett-Packard hp_laserjet_mfp_m129-m134 all-in-one
>>device `v4l:/dev/video0' is a Noname WebCam SC-13HDL11939N: WebCam S virtual device
>>but when I start xsane, I get
> "error - Failed to open device 'hpaio:/net/hp_laserjet_mfp_m129-134?ip='.
>>Error during device I/O
> Sorted this but the results are interesting.
> 1 I couldn't find any logs of the error. I finally found it's logging
> to /var/log/syslog, whereas everything on a Slackware system logs to
> /var/log/messages. Is syslog coded in?

The hpaio backend is a third party backend so it may be doing something
different but (some of) the sane-backends logging uses the syslog and
vsyslog C functions for its logging.  This means your syslog daemon
(mine's rsyslog) decides where it ends up based on the log message's
priority and facility.

> 2 There, I found these:
> Aug 4 17:12:53 RoseViolet xsane: common/utils.c 245: unable to load library libm.so: /usr/lib64/libm.so: invalid ELF header
> Aug 4 17:12:53 RoseViolet xsane: common/utils.c 173: validate_plugin_version() Plugin version[3.19.3] mismatch with HPLIP version[3.19.6]
> Aug 4 17:12:53 RoseViolet xsane: common/utils.c 206: Plugin version is not matching
> Aug 4 17:12:53 RoseViolet xsane: common/utils.c 277: Invalid Library hanlder pLibHandler = NULL.
> The plugin was 3.19.3, hplip was 3.19.6. It didn't affect printing, but that sat down scanning.
> As for libm.so, /usr/lib64/libm.so is a 141 byte script ot header. /lib64/libm.so-2.29 is a glibc lib. I renamed the script, and created a symlink libm.so pointing at /lib64/libm-2.29.so
> and the problem vanished

As far as I'm concerned, it looks like you just swept your problem under
a rug.  Is your xsane built for the Slackware version you're using?  Is
whatever hplip/hpaio you are using built for the same?

Not that I have any experience with Slackware but the above messages
seem to indicate something's fairly badly amiss between the software
components you are using.  Of course, if you are happy with sweeping
your problems under a rug, you're all set.  Just be aware that things
may start to bite again whenever any of these are updated.

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