Bugzilla – Bug 153128
/etc/init.d/sane-dev doesn't find configured Canon LiDE 60 scanner
Last modified: 2006-02-27 15:46:53 UTC
STEPS TO REPRODUCE Plug a Canon LiDE 60 scanner to the computer, and set it up using YaST's Scanner module. WHAT HAPPENS Even though YaST tells that the scanner is properly configured and is using the "genesys" driver, the following happens: - Kooka doesn't find any scanner - /etc/init.d/sane-dev gives the following output: # /etc/init.d/sane-dev status There are no scanner device files in /var/lib/sane/devices # /etc/init.d/sane-dev start Searching for configured scanners in SANE.. No scanner device files found. done - But scanimage shows something different: # scanimage -L device `genesys:libusb:001:002' is a Canon LiDE 60 flatbed scanner # scanimage -T scanimage: scanning image of size 2574x3531 pixels at 8 bits/pixel scanimage: acquiring gray frame, 8 bits/sample scanimage: reading one scanline, 2574 bytes... PASS scanimage: reading one byte... PASS scanimage: stepped read, 2 bytes... PASS scanimage: stepped read, 4 bytes... PASS scanimage: stepped read, 8 bytes... PASS scanimage: stepped read, 16 bytes... PASS scanimage: stepped read, 32 bytes... PASS scanimage: stepped read, 64 bytes... PASS scanimage: stepped read, 128 bytes... PASS scanimage: stepped read, 256 bytes... PASS scanimage: stepped read, 512 bytes... PASS scanimage: stepped read, 1024 bytes... PASS scanimage: stepped read, 2048 bytes... PASS scanimage: stepped read, 4096 bytes... PASS scanimage: stepped read, 4095 bytes... PASS scanimage: stepped read, 2047 bytes... PASS scanimage: stepped read, 1023 bytes... PASS scanimage: stepped read, 511 bytes... PASS scanimage: stepped read, 255 bytes... PASS scanimage: stepped read, 127 bytes... PASS scanimage: stepped read, 63 bytes... PASS scanimage: stepped read, 31 bytes... PASS scanimage: stepped read, 15 bytes... PASS scanimage: stepped read, 7 bytes... PASS scanimage: stepped read, 3 bytes... PASS According to scanimage, the scanner is correctly configured and working. So why doesn't sane-dev finds it?
Please attach the YaST logfiles.
Created attachment 70017 [details] YaST's Scanner module log
Also add `hwinfo --scanner', please.
Created attachment 70022 [details] lsusb -v output showing the connected Canon LiDE 60 scanner
I have attached 'lsusb -v' output, because 'hwinfo --scanner' does not produce any output here.
sane-dev is for legacy stuff like scsi scanners, you don't need it for usb ones. Did you unplug/plug in again the scanner after you configured it? Otherwise normal users won't have permissions. If after you did that scanimage still doesn't work as user but works as root then please attach /etc/hal/fdi/policy/10osvendor/80-scanner.fdi and the output of 'resmgr dump' (as root).
I wonder how YaST was able to detect the scanner in the first place if `hwinfo' does not produce usable output... Joao: Please attach the information asked for by Ludwig.
Hi Ludwig > Did you unplug/plug in again the scanner after you configured it? I have unplug/plug in again the scanner, and now it works. I tried to configure a HP Scanjet 6200C (USB) and the same thing happened. Only after unplugging/plugging, a normal user began to be able to use it... Is this unplugging/plugging strictly necessary (in a programming perspective)? If it is really necessary, I think it is very important that YaST alerts the user that she needs to unplug/plug the scanner to start using it. Otherwise, most users will react like me: "I can't user this scanner with SuSE". Please don't mark this bug as WORKSFORME. There is still an issue here.
Hi Michael > I wonder how YaST was able to detect the scanner in the first place if `hwinfo' > does not produce usable output... Yes, 'hwinfo --scanner' doesn't produce any output in the case of Canon LiDE 60. But in the case of HP Scanjet 6200C, it does! Since 'hwinfo' is made by SuSE, should I file I bug regarding this?
Yes, unplugging it is necessary as there is no way to tell hald to apply a certain fdi file AFAIK.
According to the subject of this bug it is invalid, see commant #6 (in short: sane-dev is only for SCSI scanners). Since Suse LInux 9.3 "hwinfo --scanner" is no longer used by YaST scanner config. YaST scanner config works in full compliance to SANE and therefore it uses "sane-find-scanner" I cannot do anything in YaST or in SANE regadring udev, HAL, or whatever dynamic device setutp tools we use at the moment. To avoid that this bug becomes too long and overcomplicated I close it as INVALID. Feel free to open a new one only regarding the re-plugging which seems to be needed to make dynamic device setutp happy but perhaps it cannot be fixed because it works as the dynamic device setutp is designed.
I should not copy and paste typos ... I meant "dynamic device setup".
I filed a new bug report: bug #153705