Red Hat Bugzilla – Bug 604442
sane-backends-1.0.21-2.fc12 breaks xsane
Last modified: 2010-06-17 09:42:36 EDT
Description of problem:
after upgrading sane-backends to version 1.0.21-2.fc12 scanning in gimp with xsane-gimp 0.997-3.fc12 stopped working. After downgrading sane-backends to 1.0.20-10.fc12 scanner worked again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open gimp
2. goto file->create(?, second menu item)->"xsane: select device" or "xsane: <device>"
3. in one case the scanner is found but preview is not working because it hangs. in the other case the scanner cannot be initialized.
xsane not working anymore
xsane should work
- xsane standalone also doesnt work.
- hardware is epson V500
- driver used: iscan-2.24.0-4.ltdl7.x86_64.rpm and iscan-plugin-gt-x770-2.1.1-2.c2.x86_64.rpm
I see that you use the proprietary driver necessary for your scanner model. Unfortunately I can't say what goes wrong with that and the new sane-backends library version, please contact Avasys/Epson about that. You might have a (slight) chance to find that out for yourself if you attempt to build their drivers from sources (well, sources plus binary object code).
Sorry that I can't help you more with that :-(.
So you verified that the combination of xsane and the new sane-backends package is working with scanners supported by sane itself?
I have checked it out with a flatbed scanner I own, both using xsane stand-alone and as a GIMP plugin worked with both previewing and scanning. I suspect that the proprietary driver uses sane-internal API which has changed between .20 and .21, but that's just guesswork (it contains its own copy of the sanei/ directory which defines sane-internal interfaces).
Ok, thanks. Will have a look at the epson code.