Hi, On Sat, Feb 22, 2003 at 06:54:58PM +0200, Nigel Ridley wrote: > > I'm copying this answer to sane-devel because I guess that's what you > > intended to do anyway :-)
Well, I'm doing that again. Or is there any reason to send your answers to me and not to the list? There may be better answers than mine. > > On Sat, Feb 22, 2003 at 03:22:42PM +0200, Nigel Ridley wrote: > > > > Which version of sane-backends (scanimage --version)? > > > Not sure how to get that info but this is the version of Xsane that I > > > downloaded from Debian.org: xsane 0.90-3 > > > > The version of xsane isn't important. The version of the backends > > (drivers) is interesting. I pointed you to how to get it in brackets > > (scanimage --version). You could also use apt-cache show libsane for > > Debian. > nigel@nigels_box:~$ scanimage --version > bash: scanimage: command not found It's in sane-utils. If you don't need scanimage (command line frontends) or sane-find-scanner you won't need that. > nigel@nigels_box:~$ apt-cache show libsane > Version: 1.0.11-2 Ok, that's latest. I hope that's the one you have installed. > Version: 1.0.7-3.2 That ooold :-) > > Maybe scanimage and sane-find-scanner isn't installed? apt-get install > > sane-utils > root@nigels_box:/home/nigel# apt-get install sane-utils > Reading Package Lists... Done > Building Dependency Tree... Done > Package sane-utils has no available version, but exists in the database. How did you install SANE? If you use sid or woody/testsing and the packages from Aurelian you should have this package. > T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 5 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1 > P: Vendor=04a5 ProdID=20b0 Rev= 1.20 > S: Manufacturer=Color > S: Product= FlatbedScanner 23 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner Looks fine. > I hope the above isn't too much info ;-) There is no such thing as too much info :-) If I understand you cirrectly, there is no problem, and the scanner just takes some time to respond to commands after plug-in. Rebooting gives enough time so you don't notice it in this case. Bye, Henning
