#193 Scan Mode resets to Lineart/75dpi after every scan, and doesn't restore the correct mode from a saved profile (Epson WorkForce 845)

[Stephen Kent]

I am connected to an Epson WorkForce 845 multifunction unit over ethernet.

SANE/gscan2pdf detects this device automatically once the drivers are installed. (Driver installation instructions: Install the "lsb" package, download the epson-201107w printer driver from openprinting.org (www.openprinting.org), and install the driver package on your system.)

In the Scan dialog, under the "Scan Mode" tab (second tab), gscan2pdf defaults the scan mode to Lineart and the resolution to 75dpi (Screenshot).

This is a somewhat useless scan mode, but I can set and scan with useful settings (color/300dpi) (Screenshot). The problem though is the scanner resets to this mode after every scan (meaning, after every page when I am using the flatbed scanner and not the ADF).

These settings also either don't appear to be saved or don't load properly when saving a scan profile. I can set the scan mode to color/300dpi and save the scan profile, but when I restore that profile the scan mode and DPI settings are unchanged from their defaults (Lineart/75dpi).

Host: Linux Mint 17.1 "Rebecca"
gscan2pdf version: 1.3.0-0~ppa1 (installed from the official gscan2pdf PPA located at https://launchpad.net/~jeffreyratcliffe/+archive/ubuntu/ppa)

[Stephen Kent]

Another piece of information: I have "Cycle SANE handle after scan" checked in the Preferences dialog. What may be happening is gscan2pdf forgets what the scan settings are while it's refreshing the SANE handle. While it is reopening the device (with the "Opening device" activity bar at the bottom of the main window), all the tabs except "Page Options" in the Scan dialog temporarily disappear.

This unfortunately doesn't explain why selecting the saved the scan profile doesn't restore the correct scan settings.

[Jeffrey Ratcliffe]

Please start gscan2pdf from the command line with the --log=log option, reproduce the problem, and post the log file

[Stephen Kent]

I just reproduced the issue, attached is the requested log file (epson.log).

The logged session went as follows:

• I started gscan2pdf with "Cycle SANE handle after scan" disabled
• I scanned 1 page at Color/300dpi
• I enabled the "Cycle SANE handle after scan" option
• I scanned 1 page at Color/300dpi
• gscan2pdf refreshed the SANE handle
• The scan mode had reverted to Lineart/75dpi
• I reset the settings to Color/300dpi
• I scanned 1 final page at Color/300dpi

[Stephen Kent]

Here is a second log file in which I tried to load a saved scan profile (epson-profile.log).

This session went as follows:

• I started gscan2pdf
• Observed the scan mode setting was set to Lineart/75dpi
• Loaded my saved scan profile that I created from a previous session when the scan mode was set to Color/300dpi
• Observed the scan mode settings were still set to Lineart/75dpi

I am not certain if the saved profile contains the correct settings or not, so I'm not sure if the bug here is with profile creation or loading settings back from a saved profile.

[Bob Briscoe]

I had a similar problem. gscan2pdf would save 'page options', but it would not save scan options (e.g. brightness, contrast, resolution) between sessions, and it would not save them in a profile either, even for use within the same session. I did not have the problem you had where it forgot scan options between every scan though.

Nonetheless, I thought you might want to try something I discovered by random chance. If I name a saved profile as 'default' it uses this profile (including scan options) when a new session starts.

My config:
Epson Stylus Photo PX810FW All-in-one, connected direct to fixed ethernet.
Linux, Ubuntu 14.04.02 LTS on a Lenovo Yoga 3 Pro laptop
gscan2pdf v1.2.3 patched with http://sourceforge.net/p/gscan2pdf/bugs/173/

I'm now very happy with gscan2pdf. Even impressed.

It took a while to find good settings. Nonetheless I like the way you can set up a workflow, but selectively change it for individual pages before saving the document.

[Jeffrey Ratcliffe]

The code handling scan profiles was hugely improved in recent versions. Can you test a version newer that 2.1.1 and see if it has solved your problem?