[sane-devel] problem launching sane

[Oliver Schwartz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

> > I'm not a hacker at all so I'm not
> > proficient in interpreting the log, but it seems that sane tries
> > to add simultaneously a SCSI (bad) as well as a USB device
> > (good). 

That's not a problem. The backend will try to autodetect supported 
devices, regardless of SCSI and USB. 

> > Trying to add SCSI seems to be the problem. So I think
> > the solution will be to out-comment adding the scsi device, but
> > where and how?

What exactly is your problem? The log you sent looks fine, but it's 
incomplete. Your scanner is detected correctly. BTW, what scanner 
model are you using?

> > Or do I need to go into a total different direction?

Check if you need to specify a firmware file for your scanner (see 
http://snapscan.sourceforge.net ). If so, place the filename with 
full path of the firmware file in snapscan.conf (after the keyword 
firmware), e.g.

firmware /usr/local/sane/u34v110.bin

The firmware part of your snapscan.conf looks a bit messed up, 
although all entries are commented out. You do not need to include a 
reference to acerfirm or agfafirm.

Other sources of information is the output of "scanimage -L" and 
"SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log" (which will create a file 
"debug.log" with all the debugging information from the backend.

- -Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFAL8Rb/V6sbrmfIuMRAr0fAJ9nVkZZvXg7c4jfns3rr6YxL4l7AgCfRgm9
tP5uOQieiGHCdYgOw/ZnqGM=
=XbNZ
-----END PGP SIGNATURE-----