Jeffrey Ratcliffe

Wrong page resolution when backend has inactive x-resolution/y-resolution options (300 dpi scan saved as A6)

Thanks. I've pushed the patch to the PPA. It's building now: https://launchpad.net/~jeffreyratcliffe/+archive/ubuntu/ppa/+packages

Thanks for the feedback. I can certainly ship the patch in the PPA. I would prefer to upstream it, though, but the python3-sane maintainers seem to be ghosting me. If you can add your voice to the bug report and pull request, perhaps you can help change that.

I am about to deprecate gscan2pdf as scantpaper is stable. Please test: https://github.com/carygravel/scantpaper

My read on your symptom The code demonstrably sets source = FlatBed. If the device still feeds the ADF when paper is sitting in it, that’s the Brother MFC-J6920DW’s physical behaviour — the hardware prioritises the feeder regardless of the SANE source option. Since gscan2pdf also just sets the same source option (scantpaper is its rewrite), I’d expect gscan2pdf to behave identically — i.e. it’s not scantpaper-specific. That’s consistent with the “probably brother specific” hunch, but I can’t confirm...

Multipage scanning default selection

The New button (appearance is theme-dependent - on my systems there is no +) will let you clear the pages. If they have not been saved, you should see a dialogue asking you "Some pages have not been saved. Do you really want to clear all pages?" If you hit OK, all pages will be cleared. The new menu selection triggers the same functionality. In order to give me more information to assess #2 and #3, please start scantpaper from the command line with the --log=log option, reproduce the problem, quit,...

The fix is simple - when saving, in the save dialogue, you select pages=all, rather than pages=selected. The behaviour is identical to gscan2pdf.