It looks like this scanner does not "speak" the ESC/I protocol. At least not any flavor that the EPSON backend supports. Maybe Olaf can shed some light on this.
Karl Heinz On Oct 14, 2004, at 7:30 PM, Matt Reuther wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thursday 14 October 2004 01:32 pm, Henning Meier-Geinitz wrote: > > [SNIP] > >> Ok. Just to be safe, comment out "v4l" in dll.conf. > > Done. > > [SNIP] > >> If you start gimp from a console window, I guess you would have seen >> an error message or even a debug trace. >> >> The log still points to reading the option descriptor but I'm not sure >> if it's an xsane or epson backend problem. > > I ran gimp from the console and captured a log. It's attached. All I > did in > gimp was pick File -> Acquire -> Xsane: epson:libusb:004:002, and then > quit. > >> Checking if it happens with scanimage may help. >> >> Try something like >> export SANE_DEBUG_EPSON=255 >> scanimage -d epson -y 50 -x 50 >/tmp/image.pnm 2>log > > I did this and attached the output. > >> If it's an xsane problem, setting XSANE_DEBUG=something may also help. >> However, that can create "insane" amounts of logs. > > Let me know if you want me to try this. > >> Bye, >> Henning > > Matt > - -- > Matt Reuther > [email protected] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFBbwwXFse4xrb7oagRAnAYAKD6ONSmY12lFijcOxMYa0EgPX29XwCfReot > RNpjsAqHKVYzK3RfUukRTSY= > =UUEv > -----END PGP SIGNATURE----- > <scanimagelog-epson4180.txt.bz2><gimplog-epson4180.txt.bz2>
