The problems has disappeared. xsane and scanimage work fine now:
- The xsane gui offers scan resolutions up to 9600 dpi
- No compression artefacts, tested with 1200 dpi
- No error messages are displayed by xsane
The reason is a mystery, neither any sane nor brscan related packages seem to have been updated in the meantime, but the options xsane offers and how it behaves are clearly different. I can't remember having touched any scanner related configuration since then.
However, even though there is only one device, which is connected via WLAN, xsane offers me two "devices" upon startup:
The problems has disappeared. xsane and scanimage work fine now:
- The xsane gui offers scan resolutions up to 9600 dpi
- No compression artefacts, tested with 1200 dpi
- No error messages are displayed by xsane
The reason is a mystery, neither any sane nor brscan related packages seem to have been updated in the meantime, but the options xsane offers and how it behaves are clearly different. I can't remember having touched any scanner related configuration since then.
However, even though there is only one device, which is connected via WLAN, xsane offers me two "devices" upon startup:
Brother *b20210821 MFC-L2710DW [brother4: net1;dev0]
and
ESCL Brother MFC-L271 flatbed scanner [escl:http:// 192.168. 178.26: 80]
With the first "device", "Brother *b20210821", scanning works fine, with the second device "ESCL Brother MFC-L271", the old problems occur.