[Bug 229250] New: regression: yast2-scanner refuses to accept the scanner it finds
https://bugzilla.novell.com/show_bug.cgi?id=229250 Summary: regression: yast2-scanner refuses to accept the scanner it finds Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de yast2 scanner easily locates and identifies my scanner, an Epson CX5400. What I see is this: under 'Driver' I see only one entry: 'Not configured:' and under 'Scanner' I see 'EPSON USB MFP USB scanner (vendor=0x04b8 [EPSON], product=0x0808 [USB MFP]) at libusb:003:003' I choose 'Edit'. I see the correct entry highlighted and simply choose 'Next'. it sets up the driver, 'epson'. When it is done, I choose 'Next'. Now I see two entries: the same as above, and below it, I see under 'Driver' the text 'epson'. Under 'Scanner' I see 'No scanner recognized by this driver'. Rinse, lather, repeat. I should also note two things: 1. This worked perfectly in 10.0 and 10.1 2. sane-find-scanner does locate the scanner just fine: frank:~ # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04b8 [EPSON], product=0x0808 [USB MFP]) at libusb:003:003 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. frank:~ # 3. despite sane-find-scanner, *none* of the scanimage or other sane programs find it. This is most frustrating. I don't know if this is a HAL bug, a SANE bug, or what. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jsmeix@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jnelson-suse@jamponi.net ------- Comment #1 from jsmeix@novell.com 2006-12-20 01:09 MST ------- It is no bug in YaST because it works exactly as it should according to the data in the model decription files of the "sane" package, for background information see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 There are two drives which may support it: epson for the "Epson CX-5400" with USB-ID 0x04b8:0x0808 and epkowa for the "Epson Stylus CX5400" with USB-ID 0x04b8:0x0801 Note the confusion with model name and USB-ID. I guess that there is only a USB-ID confusion and that epkowa driver also supports it. Try the epkowa driver. To debug why the epson driver does not work for your model (it works for my Epson scanners), see http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2 "Trouble-Shooting (Debugging)" and note the help text in YaST about this particular problem: ------------------------------------------------------------------ If a driver is set up but no scanner is recognized by the driver, possible reasons are: The scanner is not connected or switched off, the driver is not the right one for the particular model (even small differences in model names or internal differences in the same model series may require different drivers), there are low-level (kernel related) device communication problems (e.g. a low-level USB problem or a low-level SCSI problem). ------------------------------------------------------------------ Note that the most often problem which is reported by users regarding scanner setup is when a driver was set up but then no scanner was recognized by this driver. If the driver is the right one for the scanner, it is often a low-level (kernel related) device communication problem (i.e. a low-level USB problem or a low-level SCSI problem) which should show up as "I/O error" or similar messages in debugging mode: To debug the epson driver, run as root: export SANE_DEBUG_DLL=4 export SANE_DEBUG_SANEI_USB=128 unset SANE_DEBUG_EPKOWA export SANE_DEBUG_EPSON=128 scanimage -d epson:libusb:003:003 -T &>/tmp/epson.debug To debug the epkowa driver, run as root: export SANE_DEBUG_DLL=4 export SANE_DEBUG_SANEI_USB=128 unset SANE_DEBUG_EPSON export SANE_DEBUG_EPKOWA=128 scanimage -d epkowa:libusb:003:003 -T &>/tmp/epkowa.debug Note that "libusb:003:003" must match to what sane-find-scanner shows you (the numbers may change from time to time). Attach the output of both above "scanimage ..." calls (i.e. the files /tmp/epson.debug and /tmp/epkowa.debug) as two attachments with mime type "text/plain" to this 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 ------- Comment #2 from jsmeix@novell.com 2006-12-20 01:17 MST ------- By the way: Each driver has a hardcoded built-in list of USB device IDs of those models for which the driver works. Both the epson driver and the epkowa driver can be forced to work for any USB ID - see "man sane-epson" and "man sane-epkowa" and the comments in the matching driver config files /etc/sane.d/epson.conf and /etc/sane.d/epkowa.conf: ------------------------------------------------------------------------ For any USB scanner not known to the backend (yet), you may, at your own peril(!!), force the backend to recognise and use it via libusb. ------------------------------------------------------------------------ -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 ------- Comment #3 from jnelson-suse@jamponi.net 2006-12-20 20:02 MST ------- Created an attachment (id=110637) --> (https://bugzilla.novell.com/attachment.cgi?id=110637&action=view) Epson Debug sane-find-scanner: found USB scanner (vendor=0x04b8 [EPSON], product=0x0808 [USB MFP]) at libusb:003:005 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 jnelson-suse@jamponi.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jnelson-suse@jamponi.net | ------- Comment #4 from jnelson-suse@jamponi.net 2006-12-20 20:29 MST ------- I added the following to /etc/sane.d/epkowa.conf after installing iscan-free: usb 0x04b8 0x0808 and scanimage -d epkowa:libusb:012:002 -T &>/tmp/epkowa.debug appears to work. Thank you. Why does it work like this? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jnelson-suse@jamponi.net ------- Comment #5 from jsmeix@novell.com 2006-12-21 02:10 MST ------- Excerpt from attachment #110637: --------------------------------------------------------------------------- [sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x0808) interface 0 at libusb:003:005 .. [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0808 .. [sanei_usb] sanei_usb_open: opened usb device `libusb:003:005' (*dn=0) [sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, productID: 0x0808 [epson] Found valid EPSON scanner: 0x4b8/0x808 (vendorID/productID) .. [sanei_usb] sanei_usb_close: closing device 0 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x080d .. [dll] init: backend `epson' is version 1.0.246 [epson] sane_open(libusb:003:005) [epson] Error opening the devicescanimage: open of device epson:libusb:003:005 failed: Invalid argument --------------------------------------------------------------------------- I.e. the second sane_open call fails for an unknown reason for this model (it works for my Epson Perfection 1240U). All I can do now is to inform the authors of those backends about the problem. Please provide also /tmp/epkowa.debug as text/plain attachment so that we can compare what both backends do. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 ------- Comment #6 from jsmeix@novell.com 2006-12-21 02:20 MST ------- Right now I noticed an unexpected thing: For the epson backend you had libusb:003:005 but for the epkowa backend you have libusb:012:002. Did you re-connect the scanner at the USB? When you disconnect the scanner form the USB and reconnect it at the same USB socket at the computer, only the device number would increase (e.g. from 005 to 006). The bus number (003 and 012) would only change, if you disconnect the scanner from the USB and reconnected it at a different USB socket at the computer and then the device number changes too. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 ------- Comment #7 from jnelson-suse@jamponi.net 2006-12-21 07:11 MST ------- I'll try to get the /tmp/epkowa.debug file attached tonight. I apologies, however, I neglected to mention that I did move the device (with no change in it's behavior) but *did* adjust the command-lines appropriately. Indeed, my wife and I were able to use the scanner successfully last night. I was a little frustrated to learn that for the last N versions I was using the epson driver without issue, and of course without /forcing/ the epkowa driver it wouldn't recognize it either. I suspect that there is a bug in the epson driver preventing it from working properly with my scanner - this certainly feels like an issue worth at least informing upstream about. Should they ask, I'm willing to work with them on fixing it. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 jnelson-suse@jamponi.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|jnelson-suse@jamponi.net | ------- Comment #8 from jnelson-suse@jamponi.net 2006-12-23 07:14 MST ------- Created an attachment (id=110999) --> (https://bugzilla.novell.com/attachment.cgi?id=110999&action=view) huge epkowa debug -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #9 from jsmeix@novell.com 2007-01-04 05:37 MST ------- I will report the problem upstream and I close this bug report as "wontfix" which means that I cannot fix it. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229250 ------- Comment #10 from jsmeix@novell.com 2007-03-27 03:21 MST ------- For the log: See http://lists.alioth.debian.org/pipermail/sane-devel/2007-March/018909.html -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com