On Wed, 2016-12-07 at 15:24 +0100, Johannes Meixner wrote:
See also "SANE Backends" at https://en.opensuse.org/SDB:Configuring_Scanners that reads (excerpt): ---------------------------------------------------------- If several backends are activated at the same time, there may be a conflict between the backends. If this is the case, try if it works if you only activate one backend at a time. ----------------------------------------------------------
I think I do correctly remember that I have had issues in the past in particular with Epson scanners where several backends are available that support them, free software backends in sane-backends and also the one from the non-free Epson (Avasys) Iscan software.
Nowadays one could expect even more issues with possibly conflicting by default activated sane-backends backends versus proprietary backends from scanner manufacturers (e.g. from Brother and so on).
On the other hand perhaps nowadays all "just works well" regardless how many programs communicate with one same USB scanner device - I don't know.
Perhaps when everything just works well for other Linux distributors, we could "simply change" and do the same?
At least the bug queue for sane-backends for Fedora and Debian isn't extremely long. Of course every "my scanner doesn't work" bug report might be caused by conflicting backends.
The obvious prerequirement for such a change is someone at openSUSE who will deal with possibly incoming issues if we enable several backends by default.
We could create a branch and ask people for testing for regressions.
Another question would be if, and how, "yast2 scanner" would be able to
deal with a change like that.
Best,
Martin
--
Dr. Martin Wilck