simple scan fails to scan. "unable to start scan" change scan ner gives no options

[James Sutton]

running 10.10
epson stylus cx3200
usb
reboot of pc and printer/scanner tried.
same problem in 'xsane' and 'scanner utility' packages.
the software used to work before i had to reinstall it.
  ...............
james@james-XL58laptop:~$ sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04b8 [EPSON], product=0x0802 [USB MFP]) at libusb:006:002
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

  # You may want to run this program as root to find all devices. Once you
  # found the scanner devices, be sure to adjust access permissions as
  # necessary.
james@james-XL58laptop:~$ scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
james@james-XL58laptop:~$
................

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: simple-scan 2.32.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-32.66-generic 2.6.35.14
Uname: Linux 2.6.35-32-generic i686
Architecture: i386
Date: Fri Mar 9 13:25:52 2012
DriverPackageVersions:
 libsane 1.0.21-2ubuntu2
 libsane-extras N/A
 hplip 3.10.6-1ubuntu10.2
 hpoj N/A
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2)
MachineType: ASUSTeK Computer Inc. X58L
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-32-generic root=UUID=1adaa652-ac13-4a80-9382-d57361e69748 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: simple-scan
dmi.bios.date: 09/08/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X58L
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr201:bd09/08/2008:svnASUSTeKComputerInc.:pnX58L:pvr1.0:rvnASUSTeKComputerInc.:rnX58L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: X58L
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Michael Nagel (nailor)]

This really needs to work with scanimage and xsane before it will be fixed in simple-scan. This most likely is a driver/backend issue and does not require any change in simple-scan.
Reassigning.

[Rolf Leggewie (r0lf)]

doing some triaging here. Are you guys in on the console or in X on those machines? Or via ssh or similar mechanisms?

Does "sudo scanimage -L" work?

[jerico (jerico-dev)]

Same problem here with a different printer:

#> sane-find-scanner

found USB scanner (vendor=0x04e8 [Samsung], product=0x341b [SCX-4200 Series]) at libusb:003:008

#> sudo scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

[jerico (jerico-dev)]

A few more pieces of information...

Seems to be a regression:
- The scanner does not work under Ubuntu 12.04.3 (kernel 3.8.0-31-generic)
- The same scanner works perfectly with a different computer running Ubuntu 12.04 (kernel 3.2.0-54-generic)

I found out that when I plug in the scanner then scanimage -L will actually give me a result the first time:
"device `xerox_mfp:libusb:003:013' is a SAMSUNG ORION multi-function peripheral"

I only get the above error message from the second time onwards when I'm executing scanimage -L.

[Rolf Leggewie (r0lf)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Jerico, it's best you open your own ticket about this.

[John (webdevelopmentusa)]

I'm getting the same error on a fresh upgraded 18.04 LTS Ubuntu. It just scanned fine in Elementary OS on my laptop with the same scanner but I need it to work on my desktop that has Ubuntu 18.04 but it failed.

The scanner made a noise for 1 second then stopped and the error appeared.

[Miles (taintedsushi)]

Similar issue here with Elementary Loki. Scanner warms up to scan then errors with "Unable to start scanner"

Scanner is detected with scanimage -L

Running scanimage > output.pnm produces the error "sane_start:Error during device I/O"

[Rolf Leggewie (r0lf)]

@John and @Miles, please open your own ticket, this one will not receive any further attention.

[Pablo Menéndez del Barrio (pablopicas1234)]

Hi guys, I have the same problem than John and Miles over different Epson Wifi Scanners or combis (printer + scanner). After searching a lot, many other Linux Distributions have the same problem in their latest versions with the scanner drivers well installed and the conection to the equipment working. Using the program what you want, the scanner starts (you can see the process on the scanner screen) to do his work and then all fails.

The most worrisome situation is that anyone of this forums don't give any solution and it looks like a big problem. To nornmal users and institutional or educational ines, this type of problems are very important to select a good OS, and it's crazy that in 2019 we have problems to work propperly with a modern scan in Linux, no to mention that many manufacturers like Epson still do not give direct support...

Greetings from Spain,
Pablo.

[Rolf Leggewie (r0lf)]

Pablo, I agree about the sad state of affairs. The right place to vent is at the manufacturers, mostly. To up their Linux support. Go vote with your wallet.

Without the requested information, there's nothing we can do here, so I'm re-closing.