← Back to team overview

simple-scan-team team mailing list archive

[Bug 711821] Re: Scan sensor doesn't automatically go back to initial position after scanning a page

 

This is most certainly linked to the hardware in use. Please provide the
following information:

5. Always explicitly mention the full make and model of your scanner, e.g. "HP Deskjet F4580".
6. Always provide the id, that might be determined by running lsusb and pasting the corresponding line, that might look like "Bus 001 Device 004: ID 062a:900d Creative Labs". Do not paste the full list of all other USB devices. Adapt for SCSI scanners.

Thanks!

** Changed in: simple-scan
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Simple
Scan Development Team, which is the registrant for Simple Scan.
https://bugs.launchpad.net/bugs/711821

Title:
  Scan sensor doesn't automatically go back to initial position after
  scanning a page

Status in Simple Scan:
  Incomplete

Bug description:
  Instead of going back to its default position the scanner's image sensor stays stuck at the end of the page.
  To make it go back you have to choose either:
  - save/cancel/new scan does init the scanning session
  - Scan new page too, which is a subsequent bug since you have to click another time (when the sensor has been ordered to go back to its default position) to actually scan another page.

  I don't know if this is specific to my Samsung scanner/printer (source listed as Samsung Orion), or if that was a choice to add a pause in between documents, but Xsane or scan2pdf don't hang like this.
  My workaround for multi-page documents has been to use scan2pdf: you input the number of pages beforehand and while the sensor retreats to start over scanning you have (just enough) time to change the page on the flatbed.
  Maybe some scanners are too fast and you have to put them on hold in between pages?

  If this is a known issue I suppose this is ok with most people since
  scanning is limited to 1 page most of the time. This has been an issue
  ever since I started using Simple-scan with my office config: Lucid
  64bit.

  Possibly linked to bug #667220

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/711821/+subscriptions