https://bugzilla.novell.com/show_bug.cgi?id=334764#c5
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Info Provider|wob@bermuda.ch |
Resolution| |INVALID
--- Comment #5 from Johannes Meixner 2007-10-19 01:48:26 MST ---
What looks interesting for me from the scanimage debug output:
------------------------------------------------------------------------
[sanei_scsi] sanei_scsi_find_devices: vendor=HP ...
..
[sanei_scsi] lx_chk_devicename: matched device(direct): /dev/sg1
..
[sanei_scsi] sanei_scsi_open: The device found for /dev/sg1 does
not look like a scanner
..
[sanei_scsi] sanei_scsi_find_devices: ... type=Processor ...
..
[sanei_scsi] lx_chk_devicename: matched device(direct): /dev/sg5
..
[hp] sanei_hp_device_new: /dev/scanner
..
[hp] probe_scanner: Probing /dev/scanner
..
[hp] sanei_hp_device_new: /dev/scanner: found HP ScanJet model C1130A
device `hp:/dev/scanner' is a Hewlett-Packard C1130A flatbed scanner
------------------------------------------------------------------------
The last line looks perfectly o.k. - i.e. "scanimage -L"
found your scanner as
device `hp:/dev/scanner' is a Hewlett-Packard C1130A flatbed scanner
The hp driver scans the SCSI bus for vendor=HP where it finds
/dev/sg1 but this is no scanner and then for type=Processor
where it finds /dev/sg5 which is your scanner but because of
your symlink it finally ends with the device file /dev/scanner
for your scanner.
What YaST does to find out if an autodetected scanner
(YaST calls sane-find-scanner to autodetect scanners)
is found by a driver is that YaST compares the scanner
device which is found by sane-find-scanner with the
scanner device which is reported by "scanimage -L".
In your case it is autodetected at /dev/sg5 but later
found at /dev/scanner so that there cannot be a match.
But when it is found, YaST should have reported it
according to your "scanimage -L" output like
hp | Hewlett-Packard C1130A flatbed scanner at hp:/dev/scanner
According to the above "scanimage -L" output,
your scanner is now found by the hp driver and
then it should work to do a test scanning with
scanimange -d hp:/dev/scanner -T
(the same command is called by YaST to test it in YaST
but the precondition is that "scanimage -L" found it).
Either it was a temporary problem (from my HP ScanJet 6200C
I know that it takes sometimes more than one minute after
switching on the scanner until it becomes ready to respond)
because meanwhile "scanimage -L" finds your scanner
or perhaps your symlink leads to confusion because there are
two device file names which point to the same device.
From my current point of view there is no bug.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.