Hi,
On Sat, May 12, 2001 at 08:51:32PM +1200, Glenn Ramsey wrote:
> I just had a similar thing happen. scanimage -L was finding the
> scanner but xscanimage and xsane would not find it. I had some
> config files from an old debian package in /etc/sane.d which I
> removed. Then I made a link from /usr/local/etc/sane.d to
> /etc/sane.d and that fixed the problem.
The backend from the SANE package at www.mostang.com/sane will only
use /usr/local, not /usr or /etc if configured without any changes.
So if a backend uses /etc/sane.d/something one of the following may be
true:
* the backend is not from the original sane package (e.g. it's from
the distribution (maybe somewhere in /usr/local/lib/sane)
* there was an option given to configure (maybe a variable works, too)
* SANE_CONFIG_DIR was set.
You can see the search path for the config files if you look at your
backend's man page (e.g. man sane-mustek) at the section environment->
SANE_CONFIG_DIR.
> Also if I do not link /usr/local/etc/sane.d to /etc/sane.d then
> xsane and xscanimage still do not find the scanner. Anyone know
> why this is? Versions are xsane 0.76 and sane 1.04.
Library problems maybe. What's in /etc/ld.so.conf? What's the output of
SANE_DEBUG_DLL=255 xscanimage
Bye,
Henning
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sat May 12 2001 - 03:42:57 PDT