[sane-devel] Xsane Crashes with Epson 4180 Scanner
Fri, 15 Oct 2004 10:37:39 +0900
Karl Heinz Kremer <firstname.lastname@example.org> writes:
> 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.
I guess I could ;-)
As the EPSON drivers say, this is a GT-F600. It does not speak ESC/I.
It will be supported by iscan's epkowa backend in the near future (but
first we'll get a release for a bunch of all-in-ones).
FYI, it is closely related to the GT-9400 (Perfection 3170 PHOTO)
which is supported as of iscan-1.6.0.
> 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:
>>> Ok. Just to be safe, comment out "v4l" in dll.conf.
>>> 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
>>> 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.
>> - --
>> Matt Reuther
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (GNU/Linux)
>> -----END PGP SIGNATURE-----
Olaf Meeuwissen EPSON KOWA Corporation, PF1
FSF Associate Member #1962 sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2