[SOLVED] SimpleScan not working with scanner; unable to scan

[Pointedstick]

I can't seem to get SimpleScan to work with my flaltbed scanner, a Canon LiDE100. When I try to scan, it displays a red bar with the text "Failed to Scan. Unable to start scan." I've got my scanner selected and everything. Running it sudo'd or as admin doesn't hep, and running the binary from the command-line displays the following error:

** (simple-scan:4350): WARNING **: scanner.vala:1098: Unable to start device: Error during device I/O

What am I doing wrong?

[kyphi]

You have two options:

1. follow these instructions - "http://robsworldoftech.blogspot.com.au/ ... tu-or.html".
2. download the scanner driver from here: "http://www.sane-project.org/sane-mfgs.html#Z-CANON".

[omerderi]

I had a similar problem with my Genx Flatbed Scanner 1200 which had been detected as "Plustek OpticSlim 1200" in Linuxmint 12.

I downloaded the Windows driver from the manufacturer's website, then used "Wine" to install it in C\Program Files\ of my Windows partition, then copied the firmware file named "CISM216.FW" to the: /usr/share/sane/gt68xx/ directory of my Linuxmint system-according to the useful information I found on this website: http://linux.die.net/man/5/sane-gt68xx.
After that my scanner worked fine with both "Simple Scan", and "Xsane Image Scanning Program" utilities of Linuxmint 12.

[comfyred]

I previously had SANE/SimpleScan working fine with my Canon LIDE 200.

Today when I connected the scanner SimpleScan recognized it, but would not scan, similar to the OP's problem.

SimpleScan is obviously communicating with the scanner (I can hear it), and SANE recognizes the scanner through the terminal. (scanimage --help)

I was able scan successfully with this input to the terminal:

scanimage -d genesys:libusb:002:004 --format=tiff >image.tiff

I hope this is mildly helpful to someone.

[Pointedstick]

In the end, in Mint 12, my problem was solved by following the instructions on http://robsworldoftech.blogspot.com.au/ ... tu-or.html

In the Mint 14 RC, the problem doesn't exist in the first place!