[sane-devel] Problems with sane and USB
Olaf Meeuwissen
olaf.meeuwissen at avasys.jp
Tue Nov 7 00:24:33 CET 2006
cl at isbd.net writes:
> On Mon, Nov 06, 2006 at 09:19:38AM +0000, cl at isbd.net wrote:
>> On Sat, Nov 04, 2006 at 07:12:39PM -0500, m. allan noah wrote:
>> > On Sat, 4 Nov 2006 cl at isbd.net wrote:
> [snip]
>> > >
>> > >If I run "scanimage -L" as root it says "No scanners were identified".
>> > >
>> > >If I run "xsane" or "xscanimage" as root they find both my scanners.
>> >
>> > the fact that scanimage does not work, but xsane does, generally means
>> > that you have two copies of sane-backends installed, often the distro's
>> > original one, and one in /usr/local
>> >
>> Ah, thanks, it's possible that I do have two copies of sane installed,
>> I'll investigate.
>>
> It's not that I have two copies of sane installed, it's the various
> "add-ons" that have screwed things up. It would appear that both the
> HPLIP/CUPS installation and the iscan installation have assumed a base
> directory of /usr/local whereas the basic sane installation is in
> /usr.
The iscan RPMs use /usr (and are not relocatable). If you compiled
from source, the ./configure script is GNU standards compliant and
uses /usr/local as the default prefix. A look at:
$ ./configure --help
would have told you that. You can easily recompile for /usr with
# ./configure --prefix=/usr
> The result is a right hodge-podge of things in the wrong places.
>
> It's *very* obvious why iscan doesn't work, I'm still less lear about
> why "scanimage -L" doesn't work, as suggested I think I'll maybe try
> uninstalling and then re-installing everything with "where to install"
> set to the same place for all.
Hope this helps,
--
Olaf Meeuwissen EPSON AVASYS Corporation, SE1
FSF Associate Member #1962 sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2
More information about the sane-devel
mailing list