sane does not overwrite your already installed config files.
allan
On Sat, Mar 7, 2015 at 3:57 AM, Rafe DiDomenico <rafe...@gmail.com> wrote:
> Thanks again Paul,
>
> So, running the first check ("export SANE_DEBUG_GENESYS=10") returns
> nothing.
>
> I checked the genesys.conf and find no mention of the 220 in there.
>
> I checked the git folder and "pull" says it's "already up-to-date."
>
> I must not have the newest backend for some reason (I used
> git://git.debian.org/sane/sane-backends.git). Is the genesys backend not
> responding a problem, or is that just because it's not using it?
>
>
>
> On 03/06/2015 07:52 PM, Paul Newall wrote:
>
> On 06/03/15 09:44, Rafe DiDomenico wrote:
>
> Just for fun, I rebooted and tried everything again. Now I get:
>
> rafe@office:~$ find /usr -name libsane.s*
>
> /usr/lib/libsane.so.1.0.25
> /usr/lib/x86_64-linux-gnu/libsane.so.1.0.25
> /usr/lib/x86_64-linux-gnu/libsane.so.1.0.24
> /usr/lib/x86_64-linux-gnu/libsane.so
> /usr/lib/x86_64-linux-gnu/libsane.so.1
> /usr/lib/libsane.so
> /usr/lib/libsane.so.1
>
> So it is in x86...
> Find-scanner identifies the scanner, but still getting no further.
>
> found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan],
> chip=GL848+) at libusb:002:002
> # Your USB scanner was (probably) detected. It may or may not be supported
> by
> # SANE. Try scanimage -L and read the backend's manpage.
>
> # Not checking for parallel port scanners.
>
> # Most Scanners connected to the parallel port or other proprietary ports
> # can't be detected by this program.
>
> rafe@office:~$ sudo scanimage -L
>
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
>
>
>
>
>
> rafe,
> So I'd say your current situation is that you have sane installed in a
> couple of places (usr/lib and usr/lib/x86_64-linux-gnu)
> and you are running a version of 1.0.25
> I think the genesys backend is supposed to support your lide 220 scanner, so
> I'd now do this in terminal:
> ...$ export SANE_DEBUG_GENESYS=10
> ...$ scanimage -L
> the first line causes the genesys backend to output debug information when
> you run scanimage, a higher number gives more detail.
> So you should see some debug info as scanimage looks for the scanner. (If
> you see nothing the genesys backend is probably not enabled)
>
> If the backend is being run by scanimage, but not finding the scanner:
> Look at the file /etc/sane.d/genesys.conf to see if it has the lines
> # Canon LiDE 220
> usb 0x04a9 0x190f
> if not your version of sane may not be new enough.
>
>
>
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-requ...@lists.alioth.debian.org
--
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org
