After a FC2T3 install, my scanner is detected by: sane-find-scanner found USB scanner (vendor=0x04b8 [EPSON], product=0x011b [EPSON Scanner]) at libusb:001:002 But not by: scanimage -L scanimage: no SANE devices found After adding the following line to /etc/sane.d/epson.conf it worked: # Epson Perfection 2400 usb 0x04b8 0x011b Now the scanner is detected by: scanimage -L device `epson:libusb:001:002' is a Epson GT-9300 flatbed scanner
The problem in the original bug report was fixed, but only for root. If a user wanted to work with the scanner. Several other steps had to be taken as described here: http://www.freecolormanagement.com/sane/libusb.html Would be good if FC already did some/all of these steps by default.
Please try the 1.0.13-6 package: ftp://people.redhat.com/twaugh/tmp/sane-backends/
Updated the package, also updated xsane. But now my scanner isn't even detected by the system using lsusb. rpm -q libusb libusb-0.1.8-2.1 rpm -q kernel kernel-2.6.5-1.327 kernel-2.6.5-1.350 rpm -q xsane xsane-0.92-10 rpm -q sane-backends sane-backends-1.0.13-6
Is it on? :-) Seriously, 'lsusb' is talking directly to the kernel so SANE isn't really a possible culprit at that stage.
Actually, usb 0x04b8 0x011b BROKE support for me. All I needed to make it work was usb and then I could scan again.
Aha. Kees, does just having 'usb' work for your scanner work as well?
"usb 0x04b8 0x011b" works for me but I found that I can only use the scanner if i replug the device before starting xsane. Think that this activates the hotplug scripts. If I reboot, then start xsane, it won't detect the scanner (but lsusb says it's there). If i unplug and then reinsert the scanner, xsane will detect the scanner. Strange.
The problem with lsusb not detecting the scanner was solved by replugging the external power supply and usb cable to the scanner.
No, this is expected. But I need you to test this line: usb
yes, that works for xsane. (after replugging the scanner)
[This is a mass update sent to many bugs that missed earlier such messages due to having their version set to a test version.] This bug was originally filed against a version of Fedora Core which is no longer supported, even for security updates. Many changes have occured since then. Please retest this bug against a still supported version. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. If it still occurs on FC5 or FC6, please assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. This bug will be closed after a few weeks if no information is given indicating that the bug is still present in a supported release.
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.