auv-ee

Thanks again. Yes, still on F31 because it sometimes takes time to recover my work-flow after major upgrades, due to some legacy software that I use. I try to upgrade every-other release to minimize disruption in the middle of large projects.

Thanks for the info about locale, I'm certainly not very familiar with that (I'm firmly stuck in 7-bit ASCII ;-) ). I DO prefer to install from repository, but that is still at 2.7.0, and I need to try 2.9.0 before reporting a different bug. Thanks for the info that Fedora patches-out the pdftk warning. That explains why it started cleanly in the past.

My locale returns: LANG=en_US LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT="C" LC_IDENTIFICATION="C" LC_ALL=C (For various reasons, the C locale is helpful to me.) Without the above patch, gscan2pdf thinks the locale is blank, in other words: ''. With the patch, it thinks my locale is 'C', rather than 'en_US'. If I revert the patch, and set the environment variable LANGUAGE to en_US,...

I have just tested with 2.6.7. I can report that the geometry settings now work as expected. Thank you. I have retested with the HP OfficeJet Pro 8720, and as before, the page selection still works for flatbed, ADF and ADF-Duplex scans. I have retested with the Fujitsu ScanSnap iX500, and it now works perfectly switching between US legal and US letter. I note that when I select a pre-set size, such as US Letter or US Legal, that subsequently selecting Manual now displays the dimensions of the of...

No appology needed. As I review my test, above, the HP worked fine, with the geometry changing as expected. Perhaps the log file shows some remaining issue, but I included it for comparison: Fujitsu not working, HP working. The two devices have quite different capabilities, and display correspondingly different options in the various tabs, so it is not surprising that they stress different aspects of gscan2pdf. I still don't know whether the settings seen in "Manual" are intended to track the last-selected...

Thanks. I guess that means I should standby...

This sounds very similar to my issues reported in Bug 346.

Well, make did perform the cp to blib, if that helps. I reexecuted with PERL5LIB="blib:blib/arch:lib:$PERL5LIB" perl bin/gscan2pdf --log=log, and the result is the same, as you suspected: the behavior is the same as without the patch. I think at this point, what makes sense is to say something in the help file about the meaning of the progress bar. Thanks for your attention.