Comment 20 for bug 891586

Revision history for this message
2CV67 (2cv67) wrote : Re: Resolution control not working

"additionally you might try to acquire a scan at a different resolution via scanimage"

Sorry to be so slow responding, but I am allergic to terminal & so Scanimage has been a difficult experience...

I did eventually get scanimage to produce its default image, using:
"chris@Acer-desk:~$ scanimage >scan-file.pnm"
This image was 26MB - the same size as iScan / 300dpi / color document / .pnm.

Much later, after many failed attempts, I think I discovered the right command for 150dpi, with this result, showing that scanimage uses the nearest "default" resolution:
"chris@Acer-desk:~$ scanimage --r 150 >scan-file2.pnm
scanimage: rounded value of resolution from 150 to 300"

That produced another 26MB image, but terminal never came back to a prompt.
When I tried to close terminal, I got a warning that a process was still running & I had to kill it to exit, which I did.
After that, the scanner could not be stopped on the button until the next reboot & no scanning was possible with any program as the scanner was "busy" or whatever.

Now, even after cold reboots & even after only a basic "$ scanimage >scan-file.pnm" scanimage never gets back to a terminla prompt & I have to kill process to exit terminal every time!

Next, I went to see how it worked in Ubuntu 10.04LTS which multiboots on the same PC & Scanner & where I have never tried scanimage.
I simply tried "$ scanimage >scan-file.pnm" which produced a 25MB image as expected but, surprisingly for me, failed to return to a prompt & forced me to kill process to exit terminal...
This sounds as though I have now screwed up something inside the scanner, doesn't it?

Fortunately, iScan & Simple Scan & XSane seem unaffected as long as I don't use scanimage.

So I suppose I try sane-devel now...