On 3/15/2022 7:15 AM, ael wrote:
In fact there are still outstanding problems which are mentioned
earlier in this bug.
Separate problems need to be tracked in separate bugs, even if they
affect the same hardware.
Please see: https://www.debian.org/Bugs/Reporting
This bug in Debian was reported by Hans Georg Colle when using
sane-backends version 1.0.32-4. It was fixed by a upstream change to the
epson2 driver in sane-backends version 1.1.1, related to setting the
focusSupport flag on specific hardware. He has confirmed this fix.
https://gitlab.com/sane-project/backends/-/issues/445
https://gitlab.com/sane-project/backends/-/merge_requests/604
Wolfram Sang, the upstream maintainer, is aware of the remaining bugs.
I infer that he hasn't had time to track them down as yet, but he has
said that he is investigating.
The same is true upstream: different problems in each backend are
tracked as separate issues. It is more helpful to the upstream
maintainers to use their issue tracker to report and follow individual
issues, rather than their mailing list. It avoids that question by
making clear the status of each issue.
https://gitlab.com/sane-project/backends/-/issues
As I recall, the main problem is with very large scans which fail.
Less important is that xsane "hangs" when the [CANCEL] button is
pressed instead of recovering gracefully.
It is very important to distinguish where the bugs are occurring here.
An issue should only be attributed to xsane if it cannot be reproduced
by using the "scanimage" command (or a different frontend, such as
simple-scan). The issues that have been identified so far are in the
epson2 backend. The sane backends and the xsane frontend are in two
different code bases that have separate upstream maintainers, and are
separately packaged in Debian.
https://gitlab.com/sane-project/backends/
https://gitlab.com/sane-project/frontend/xsane
Thanks for your help!
David
