[sane-devel] Re: Sane-devel digest, Vol 1 #393 - 8 msgs
Fri, 10 May 2002 19:21:30 +0200
On Thu, May 09, 2002 at 10:03:24PM +0200, Jim Newton wrote:
> hi henning et al, thanks for the information. in fact i'm already
> with setenv SANE_DEBUG_SNAPSCAN 255, and when i use scanimage -L i seem
> to get the exact imformation as before.
You should get something like this:
hmg@hmg1:/usr/src/sane-cvs/sane/sane-backends$ SANE_DEBUG_SNAPSCAN=255 scanimage -L
[sanei_debug] Setting debug level of snapscan to 255.
[snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
[snapscan] add_device(usb 0x04a5 0x2040)
[snapscan] add_device: Detected (kind of) an USB device
[snapscan] snapscani_usb_open(0x04a5 0x2040)
[snapscan] add_device: error opening device 0x04a5 0x2040: Invalid argument
If you don't get any debug output there are some possible reasons:
1) Debug output is disabled by your distributor. Bad. Probably nobody
can help to debug your problem in this case.
2) The snapscan backend isn't even loaded.
To find out, what's true try this (or the setenv variant of it):
SANE_DEBUG_DLL=255 scanimage -L
The output should look like this:
[sanei_debug] Setting debug level of dll to 255.
[dll] sane_init: SANE dll backend version 1.0.5 from sane-backends-1.0.7
[dll] add_backend: adding backend net
[dll] add_backend: adding backend abaton
[dll] add_backend: adding backend agfafocus
If you don't get any debug output, case 1 is true, otherwise case 2.
For case 2, double-check that snapsan is in dll.conf. Make sure, that
you don't have multiple installations of sane (e.g. in /usr and
/usr/local). Check the debug output of the dll backend to find out why
snapscan wasn't loaded.