[Bug 840445] New: yast does not recognize HP 2200 scanner, problem with sane-find-scanner on 64 bit systems
https://bugzilla.novell.com/show_bug.cgi?id=840445 https://bugzilla.novell.com/show_bug.cgi?id=840445#c0 Summary: yast does not recognize HP 2200 scanner, problem with sane-find-scanner on 64 bit systems Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: peter.krummrich@gmx.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 I have installed openSUSE 12.3 on two systems - 32 bit on a laptop and 64 bit on a tower PC. The 32 bit system on the laptop recognizes the HP 2200 C scanner attached to the USB port, installation with yast works fine and I can use the scanner with xsane. On the 64 bit system, the same scanner is found when I start yast rigth after booting the system, but it does not work. Xsane takes more than 5 minutes to start and scanning is not possible. If I start yast again, the scanner is not found any more. This seems to be the existing problem with sane-find-scanner on 64 bit systems, which I reported on the sane developer bug tracker: https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=314021&group_id=30186 Please try to motivate the team to continue working on the bug. I hoped that the issue might be solved with openSUSE 12.3, but it is not. The problem will most likely not only exist with the HP 2200 scanner on 64 bit systems, but most likely with several scanners using the plustek backend.There seems to be an issue with the way sane-find-scanner uses the usblib. Reproducible: Always Steps to Reproduce: 1. boot 64 bit system, start yast, install scanner, scanner is found but does not work 2. start yast again, install scanner, no scanner is found Actual Results: scanner is not installed properly on 64 bit system, cannot be used Expected Results: successful scanner installation on 64 bit system as on 32 bit system -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=840445 https://bugzilla.novell.com/show_bug.cgi?id=840445#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |jsmeix@suse.com |ovo.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.
https://bugzilla.novell.com/show_bug.cgi?id=840445 https://bugzilla.novell.com/show_bug.cgi?id=840445#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|YaST2 |Other Found By|--- |Community User Resolution| |UPSTREAM AssignedTo|jsmeix@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Summary|yast does not recognize HP |sane-find-scanner does not |2200 scanner, problem with |recognize HP 2200 scanner |sane-find-scanner on 64 bit |on a 64 bit tower PC but |systems |works on a 32 bit laptop QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #1 from Johannes Meixner <jsmeix@suse.com> 2013-09-17 15:37:40 CEST --- Because the issue is an upstream issue, see https://bugzilla.novell.com/page.cgi?id=fields.html#status and because you already reported it to upstream and because we cannot reproduce the issue (we neither have your scanner nor do we have your computers and our few scanners are found by sane-find-scanner both on 32-bit and on 64-bit systems) there is basically nothing what we can do here. Therfore I can only close the issue as "upstream". In contrast when you report the issue directly at the matching upstream project, there is a direct communication between you and the upstream authors. In particular we cannot tell free software authors who work at upstream on which issues they should work first and foremost. Something off the top of my head that might help a bit: Because it makes a difference which computer you use it could be the USB hardware in the computer that actually makes the difference. I don't think it is a real 32 versus 64 bit issue. If sane-find-scanner would not work on all 64 bit systems, we should have got very many such issue reports. Perhaps on your 64-bit system you use an USB 3.0 port while on the 32-bit system you use a more "traditional" lower speed USB port. There have been issues in the past where the maximum speed of the USB host port makes a big difference whether or not a bit older USB device works. Some older USB devices seem not to work on USB host ports that can do a high speed (regardless that theoretically it should "just work" but in practice it may not). Regarding how YaST scanner detection works: This is no issue in YaST because when the YaST scanner module autodetects scanners, it runs "sane-find-scanner" via /usr/lib/YaST2/bin/autodetect_scanners and basically "scanimage -L" (scanimage -f '%d,%v,%m;') via /usr/lib/YaST2/bin/determine_active_scanners I.e. YaST shows you what "sane-find-scanner" and "scanimage -L" show you. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=840445 https://bugzilla.novell.com/show_bug.cgi?id=840445#c2 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@suse.com --- Comment #2 from Johannes Meixner <jsmeix@suse.com> 2013-10-01 10:56:18 CEST --- I got feedback via direct mail: ============================================================================ Dear Mr. Meixner, thank you very much for your message and your comments. Especially the hint with the USB port was helpful. The scanner has a USB 1.1 interface. It was accidentally connected to a USB 3.0 port. In principle, this should not be an issue, as the 3.0 port should be compatible, but it seems that there were timing problems. I connected the scanner to a USB 2.0 port and thereby found out that the problem with my scanner was actually twofold - a problem with the USB port timing and an issue with sane-find-scanner on 64 bit systems. When the scanner is connected to an USB 3.0 port, there are also problems with long response times of the scanimage program. Running scanimage -L sometimes takes more than 20 seconds to complete on the 64 bit system. With the USB 2.0 port it finishes without delay, as it does on the 32 bit system. So this part of the problem was obviously caused by the USB 3.0 port. However, the sane-find-scanner problem still exists. Calling the sane-find-scanner version that came with the OpenSUSE 12.3 release with the -v -v options with root privileges lists the scanner as one USB device, but it does not recognize it as a scanner. This only happens on the 64 bit system, regardless of the USB port. When reporting the issue on Alioth in February, the author of sane-find-scanner has sent me an updated version. This version did recognize the scanner, but it did not work reliably. This was probably due to the USB port issue, which I was not aware of at the time I tested the updated version. Running yast with this updated version of sane-find-scanner copied to /usr/bin works fine now with the scanner connected to a USB 2.0 port. Xsane also works fine now on the 64 bit system as it does on the 32 bit system. ============================================================================ Regarding USB 1.1 scannes at USB 2.0 versus 3.0 ports I added a new section "USB Speed" to http://en.opensuse.org/SDB:Configuring_Scanners Regarding YaST scanner setup and "sane-find-scanner" versus "scanimage -L": One can set up any scanner model that is listed in the list of scanner models in YaST regardlesss whether or not the actual scanner device is autodetected via "sane-find-scanner" and also even when the actual scanner device is not connected to the computer, compare http://en.opensuse.org/SDB:Configuring_Scanners#Scanner ---------------------------------------------------------------------------- Run the YaST scanner module and check the list of models therein. You do not need to have a scanner connected to do this. Click "Add" and pretend to set up an imaginary scanner. Select the model and the driver from the list and click "Next" .. Finally the selected driver for the model gets activated. When no scanner is connected, all what happens is that the driver tries to autodetect a scanner which will of course fail in this case. ---------------------------------------------------------------------------- One reason why one can set up a scanner regardless if connected or not is that an admin should be able to set up a scanner on an end-user computer (e.g. workstation or laptop) at any time regardless if the scanner is connected or not. When "the driver tries to autodetect a scanner" it is what happens when "scanimage -L" is run. The difference is that "sane-find-scanner" tries to autodetect scanners without running various matching scanner drivers while "scanimage -L" tries to autodetect scanners by running all scanner drivers that are activated. In the end it should have worked sufficiently well if you had connected your HP 2200 C USB 1.1 scanner right from the start at a USB 2.0 port at your computer. Then you could have run the YaST scanner module and click "Add" (regardless that the scanner was not autodetected at that time) and select the scanner model manually from the list so that YaST activates its matching scanner driver and afterwards YaST runs "scanimage -L" which autodetects your scanner. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com