On Friday 11 May 2001 07:15 pm, you wrote:
> On Fri, May 11, 2001 at 11:53:55AM -0700, Paul Nixon wrote:
> > Anyway, I have *fixed* the scanner not found error I received earlier by
> > relinking libsane.so.1 to libsane-snapscan.so.1.0.4.
>
> That is almost certainly not what you wanted, even if it works. It will
> prevent you from using another non-Snapscan scanner or a network scanner.
Hi Nick,
Maybe there's something messed up in my libraries. What should libsane.so.1
be linked to? Linking it to libsane-snapscan.so.1.0.4 gets me a little
further, but I also tried libsane-dll.so.1.0.4 and that brought up all the
choices revealed by scanimage -L. However, the first one usb
/dev/usb/scanner0 core dumped xscanimage and scanned a gray-scale image (even
though color was selected) in xsane.
> It's quite possible that this is a backend problem.
Please clarify. I would have thought that since scanimage is able to produce
a perfect full-color scan (albeit 26MB) that this would indicate a frontend
problem. No?
> No, scanimage and xscanimage are separate front ends, the only similarity
> is the name and common contributors AFAIK.
You're right. It's just confusing that scanimage is part of the backends but
is in the frontend subdir.
Is there something about kernel 2.4.x that has broken Sane? This scanner used
to work perfectly on this system, and AFAIR, I only upgraded Gimp to 1.2.1
and the kernel from 2.2.17 to 2.4.1 (this fixed my USB printer).
Anyway, would like to know.
Thanks,
Paul
>
> Nick.
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
-- 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 : Fri May 11 2001 - 12:58:24 PDT