[sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble
Karl Heinz Kremer
Sun, 6 Jun 2004 09:25:29 -0400
I just left my comments in the bug report.
The Epson backend does not have information about these scanners (this
means no product ID), so they should not be recognized and therefore
the backend should not try to send any data. The only way this would
happen is, if somebody explicitly uses the "usb 0x4b8 0xXXX" entry in
epson.conf to manually add this scanner to the list of known scanners.
I don't have these scanners, so I cannot test this. I do however know
that if I add an EPSON scanner that is not yet supported (this was e.g.
the case with the Perfection 4850), the new scanner is not recognized,
and skipped during the scanner detection.
There may be something else doing on, but I don't know what yet.
I need a debug log for this case to find out what's going on.
the author of the bug report did not leave an email address, so I hope
that either my comment in the bug database, or this mail reaches the
Henning, do you know how to get in touch with Jan?
On Jun 6, 2004, at 6:07 AM, Henning Meier-Geinitz wrote:
> Everyone who gets timeouts/USB errors with these two scanners and
> sane-backends 1.0.14 please use the following workaround:
> Comment out the "epson" line in dll.conf (/etc/sane.d/ or
> The epson backend seems to try to talk to these scanners because they
> are Epson scanners. As they are supported by the plustek backend (not
> epson) the scanners don't like the epson commands and USB errors occur.
> See bug 300751 for details:
> I guess that bug didn't show up before the 1.0.14 release because the
> automatic detection for USB scanners in the epson backend wasn't
> turned on.
> sane-devel mailing list: email@example.com
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to firstname.lastname@example.org