Here a copy of my message that I also posted to https://bugs.launchpad.net/simple-scan/+bug/891586
******************************** The 3 minute freeze: http://lists.alioth.debian.org/pipermail/sane-devel/2012-February/029481.html The thing is that SANE provides two ways to set the resolution: A: "resolution" set to some value B: "x-resolution" and "y-resolution" are set to some value Simple Scan supports only method A. xsane and scanimage support A and B. Ususally this is not a problem, but the values for A are very limited with your scanner, see the next list. 2CV67 Epson Perfection V200 scanimage --resolution 300|2400|4800dpi [300] Sets the resolution of the scanned image. --x-resolution 75|300|600|1200|2400|4800dpi [300] Sets the horizontal resolution of the scanned image. --y-resolution 100|200|300|400|600|800|1200|1800|2400|3600|4800|6600|9600dpi [300] Additionally, the list of resolutions displayed in Simple Scan is not the list of resolutions supported by the hardware. The list is static, and you can select whatever you want. When scanning the next available resolution is chosen. In your case the choice is limited to 300/2400/4800 as Simple Scan only supports only method A. >From my point of view there are two things to do: 1) Simple Scan should support method B. 2) Someone with knowledge of the backend/driver should check if these lists are correct, especially if the list for method A is really that short.
