Scan all pages option doesn't stop when all pages are done

[Jack Senechal]

Binary package hint: gscan2pdf

When using the auto document feeder on my printer (HP Photosmart C7280) with the "#Pages: All" option selected, the printer doesn't stop scanning after the pages have run out. It keeps importing blank pages. The printer has essentially "crashed" at this point, as closing the scan dialog and the gscan2pdf program don't make it stop, and the printer is busy when you try to access it with the HP toolbox or other program. You have to turn the printer off and back on.

The workaround is to count the number of pages you have and enter that manually instead. It would be super if this option worked though!

Relevant Information:
-----------------------------------------

$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10

$ apt-cache policy gscan2pdf
gscan2pdf:
  Installed: 0.9.25-1
  Candidate: 0.9.25-1
  Version table:
 *** 0.9.25-1 0
        500 http://us.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

[Jeffrey Ratcliffe (jeffreyratcliffe)]

2009/3/9 Jack Senechal <email address hidden>:
> When using the auto document feeder on my printer (HP Photosmart C7280)
> with the "#Pages: All" option selected, the printer doesn't stop
> scanning after the pages have run out. It keeps importing blank pages.
> The printer has essentially "crashed" at this point, as closing the scan
> dialog and the gscan2pdf program don't make it stop, and the printer is
> busy when you try to access it with the HP toolbox or other program. You
> have to turn the printer off and back on.

Please post the output from the command line after starting gscan2pdf with

gscan2pdf --debug

I suspect that you are missing the batch-scan=yes option, which HPs
seem to need to report the out of paper signal.

[Jack Senechal (jacksenechal)]

You're correct, when I select the batch-scan option in the "Scan Options" dialog, the problem is fixed. Perhaps some logic could be added to make that happen automatically?

[Jeffrey Ratcliffe (jeffreyratcliffe)]

On Mar 10, 2009 3:17am, Jack Senechal <email address hidden> wrote:
> You're correct, when I select the batch-scan option in the "Scan
> Options" dialog, the problem is fixed. Perhaps some logic could be added
> to make that happen automatically?

The trouble is - only HPs have that option. Perhaps the question should be
better levelled at the HPLIP maintainers - why do they have that option,
when if fact I don't see a problem leaving it activated even when scanning
from the flatbed.

[Jack Senechal (jacksenechal)]

Upon further experimentation, the "source:auto" function doesn't seem to work with "batch scan:yes". It won't pick up the flatbed. I have to disable batch scanning to get the flatbed working. This definitely sounds like an issue for the HPLIP folks... they should be able to do some better auto-detection.

[Jack Senechal (jacksenechal)]

The batch-scan option makes a bit more sense in the context of the xscanimage GUI. I'm not sure it's a bug with the HPLIP package so much as a design choice.

It seems there are two options that would make gscan2pdf work fine with this printer:

1) Implement some logic like this, since it's implied you want to use the ADF if you're scanning more than one page at a time:
    if (pages == 'all' || pages > 1) {
        if (batch-scan-option-present) {
            enable batch-scan
        }
    }

2) Detect when the ADF is out of paper and stop scanning then. The xcanimage GUI shows a message "Failed to start scanner: Document feeder out of documents" when there's nothing in the flatbed, so I imagine that type of detection is possible.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

On Mar 10, 2009 11:33pm, Jack Senechal <email address hidden> wrote:
> 1) Implement some logic like this, since it's implied you want to use the
> ADF if you're scanning more than one page at a time:
> if (pages == 'all' || pages > 1) {
> if (batch-scan-option-present) {
> enable batch-scan
> }
> }

Or if you specify the ADF directly:

if (batch-scan-option-present) {
if ($source == 'ADF' or ($source == 'auto' and ((pages == 'all' || pages >
1)) {
enable batch-scan
}
}

> 2) Detect when the ADF is out of paper and stop scanning then. The

The detection is only passed onto SANE when the batch-scan option is
enabled.

I'll look at implementing option 1.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

I've committed a fix upstream. This will be released in 0.9.28.

[Leon (zima3000)]

I have the same problem with gscan2pdf 0.9.29 on Ubuntu 10.04 LTS (the Lucid Lynx) with HP Officejet Pro L7590 all-in-one.

Checking batch-scan option manually works but then the last page of the original is not completely ejected (although fully scanned) and printer gets stuck with "Scanning ... " on display. Pulling the paper out manually and pressing Cancel button on the printer fixes it. That only happens if batch-scan is checked so not a hardware issue.

Also, same as was the case for the OP, if batch-scan is checked scanner ignores the flatbed.

Please let me know if some additional information is needed.

[Travis Pew (travisp)]

I'm using gscan2pdf 0.9.31 on Ubuntu 10.10 with HP Officejet 6500. Selecting batch-scan fixes the problem, but I had to come here to learn that this is what I had to do.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

I (the author) also get this with my HP OfficeJet 6500.

Pressing cancel ejects the page, so I don't have to pull it out.
Alternatively, exiting gscan2pdf should also eject the page.

For some reason HPLIP doesn't eject the last page from the ADF until
the complete interface is closed.

I played with closing the interface after every scan job, but that
caused other problems, so I put up with hitting the cancel button, or
waiting until I exited gscan2pdf.

If you don't need the extra functionality of the libsane-perl
frontend, switch back to the scanimage frontend in Edit/Preferences.
That also fixes this problem.

[Aaron Roydhouse (aaron-roydhouse)]

Since I upgraded to 11.04 I've had this problem with gscan2pdf v0.9.31 when using libsane-perl front-end with HP OfficeJet 7410, where scanning never stops, just keeps adding empty pages, whether using flatbed or ADF.

Following the tip above I ticked 'Batch scan' under Preferences -> Advanced and the problem stopped.
Is there any reason you wouldn't watch 'Batch scan' enabled by default?

Following another tip above I changed to 'scamimage' front-end in Preferences and I also don't get the problem.

[Aaron Roydhouse (aaron-roydhouse)]

Sorry, an important caveat to my previous report:

>Following the tip above I ticked 'Batch scan' under Preferences -> Advanced and the problem stopped.

Although the infinite empty pages problem stops, the last page in the ADF never get ejected and the scanner gets stuck. I have to press the 'Cancel' button on the scanner after every scan. So selecting 'Batch scan' for HP-7410 is only a partial solution.

>Following another tip above I changed to 'scamimage' front-end in Preferences and I also don't get the problem.

So right now the only complete solution I have is to switch to using 'scanimage' front-end (also with the 'Batch Scan' option enabled - which seems to default on for 'scanimage' but default off for 'libsane-perl').

[Jeffrey Ratcliffe (jeffreyratcliffe)]

On 19 June 2011 10:21, Aaron Roydhouse <email address hidden> wrote:
> Although the infinite empty pages problem stops, the last page in the
> ADF never get ejected and the scanner gets stuck. I have to press the
> 'Cancel' button on the scanner after every scan. So selecting 'Batch
> scan' for HP-7410 is only a partial solution.

I have to do this with my HP OfficeJet. The only (programatical)
solution is to hang up the complete libsane connection and then make
another one for the next scan.

As far as I am aware, only HPLIP does this, and as pressing cancel
seemed no big deal, I hadn't yet implemented the above solution
properly (beyond checking that it worked).

[Jeffrey Ratcliffe (jeffreyratcliffe)]

On 19 June 2011 17:13, Jeffrey Ratcliffe <email address hidden> wrote:
> I have to do this with my HP OfficeJet. The only (programatical)
> solution is to hang up the complete libsane connection and then make
> another one for the next scan.

I've just implemented this. You'll see it in the next release of
gscan2pdf in a few days time

[Erho Ere (futurelanduse)]

Fedora 16, HILIP 3.11.12
device `hpaio:/net/Officejet_Pro_8600?ip=192.168.XXX.XXX' is a Hewlett-Packard Officejet_Pro_8600 all-in-one
hp-check -r -t gets no errors, flatbed scanning is working.

Same problem here, except I can't find a "batch-scan" option anywhere in gscan2pdf; scanimage --help doesn't list "--batch-scan[=(yes|no)" option available. I compiled the latest gscan2pdf, but the problem remains. Enabling "cycle SANE handle" didn't help. The stop-button now aborts the scan, which helps.

My problem might be different -- I get no image from libsane-perl with the ADF. With scanimage, I can only get an image from one page, not 2. I think something is wrong on HPLIP's end with the Pro8600.

Simple Scan is having the same issue-
https://bugs.launchpad.net/simple-scan/+bug/875647

[Amil (amilkhanzada)]

Same issue with my OfficeJet 6700.
With version 0.9.3.2 of gscan2pdf, the application would wait forever for the final page to come.

Althought it is not a complete fix, I got gscan2pdf to be able to scan all pages, but allow me to save to pdf before crashing. To do so, you need version 1.1.0, which is not in apt-get.
0. sudo apt-get remove gscan2pdf
1. Install gdebi with "sudo apt-get install gdebi"
2. Download libsane-perl https://launchpad.net/~alex-p/+archive/notesalexp-precise/+build/3598121
3. sudo gdebi libsane-perl_0.05-2+nmu1ppa1~precise1_amd64.deb
4. Download gscan2pdf_1.1.0_all.deb http://sourceforge.net/projects/gscan2pdf/files/gscan2pdf/1.1.0/
5. sudo gdebi gscan2pdf_1.1.0_all.deb
6. Run gscan2pdf and scan as before (there is still no batch-scan option I can find)

Please add the batch-scan option back into gscan2pdf! This application looks very neat, but it is hard to use due to this problem.

[Jeffrey Ratcliffe (jeffreyratcliffe)]

Please start gscan2pdf from the command line with:

gscan2pdf --log=log

open the scan dialog, quit, and post the log file