Red Hat Bugzilla – Bug 1458903
[Patch] Lack of USB3 xhci patch makes SANE quite unusable with USB3 hardware
Last modified: 2018-04-10 09:47:37 EDT
Description of problem: Lack of USB3 xhci patch makes SANE quite unusable with USB3 hardware; example with Fujitsu fi-6130 (theoretically fully supported by SANE): [root@tux ~]# scanimage -L # First run device `fujitsu:fi-6130dj:108292' is a FUJITSU fi-6130dj scanner [root@tux ~]# [root@tux ~]# scanimage -L # Second run a few moments later No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [root@tux ~]# Version-Release number of selected component (if applicable): sane-backends-1.0.24-9.el7 How reproducible: Everytime, see above and below. Actual results: Lack of USB3 xhci patch makes SANE quite unusable with USB3 hardware. Expected results: Applying upstream USB3 xhci patch solves the issue (tested myself). [root@tux ~]# scanimage -L # First run device `fujitsu:fi-6130dj:108292' is a FUJITSU fi-6130dj scanner [root@tux ~]# [root@tux ~]# scanimage -L # Second run a few moments later device `fujitsu:fi-6130dj:108292' is a FUJITSU fi-6130dj scanner [root@tux ~]# [root@tux ~]# scanimage -L # Third run a few moments later device `fujitsu:fi-6130dj:108292' is a FUJITSU fi-6130dj scanner [root@tux ~]# Additional info: https://src.fedoraproject.org/cgit/rpms/sane-backends.git/plain/sane-backends-1.0.24-usb3-xhci.patch?id=e0bd4233ccf23151f4adfa14f45f328ae57c7c20
Created attachment 1285126 [details] sane-backends-1.0.24-usb3-xhci.patch
Created attachment 1285127 [details] Patch for sane-backends.spec
Cross-filed ticket 01863749 on the Red Hat customer portal.
Hi Robert, thank you for contacting us, but it is too late to get this patch into RHEL-7.4, we will look into it for RHEL-7.5. I am deeply sorry for inconvenience.
RHEL 7.5 would be fine.
Robert, I think it would be better to include upstream commit 1207ce5a40664c04b934bd0a6babbc1575361356 too. It uses environment variable SANE_USB_WORKAROUND, which setting to 1 enables workaround, which is in your proposed patch. It could minimize impact for other users. Its usage will be explained in man page sane-usb(5). Do you agree, Robert?
Upstream issue for adding SANE_USB_WORKAROUND usage into man page https://alioth.debian.org/tracker/index.php?func=detail&aid=315792&group_id=30186&atid=410366
Robert, would you mind testing these rpms from this link https://zdohnal.fedorapeople.org/.sane/ ?
Upstream accepted manpage patch as commit 56398ead607d8bcb9deef7ca3f4d7f78478f1b4c
Created attachment 1313099 [details] Proposed patch
(In reply to Zdenek Dohnal from comment #8) > I think it would be better to include upstream commit > 1207ce5a40664c04b934bd0a6babbc1575361356 too. It uses environment variable > SANE_USB_WORKAROUND, which setting to 1 enables workaround, which is in your > proposed patch. It could minimize impact for other users. Its usage will be > explained in man page sane-usb(5). Do you agree, Robert? If the result is the same in the end, I don't mind about the details of the patch or whether to set an environment variable.
Do you still need a test for verification? Or do you have such hardware yourself around somewhere?
Yes, would you mind testing it? I do not have such HW unfortunately.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0793