Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1458903.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-06-05T19:09:13+00:00 Robert wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/0 ------------------------------------------------------------------------ On 2017-06-05T19:11:14+00:00 Robert wrote: Created attachment 1285126 sane-backends-1.0.24-usb3-xhci.patch Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/1 ------------------------------------------------------------------------ On 2017-06-05T19:15:08+00:00 Robert wrote: Created attachment 1285127 Patch for sane-backends.spec Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/2 ------------------------------------------------------------------------ On 2017-06-05T19:21:34+00:00 Robert wrote: Cross-filed ticket 01863749 on the Red Hat customer portal. Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/3 ------------------------------------------------------------------------ On 2017-06-06T07:44:23+00:00 Zdenek wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/4 ------------------------------------------------------------------------ On 2017-06-06T10:11:21+00:00 Robert wrote: RHEL 7.5 would be fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/5 ------------------------------------------------------------------------ On 2017-07-19T07:06:55+00:00 Zdenek wrote: 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? Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/6 ------------------------------------------------------------------------ On 2017-07-19T07:15:55+00:00 Zdenek wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/7 ------------------------------------------------------------------------ On 2017-07-19T11:48:42+00:00 Zdenek wrote: Robert, would you mind testing these rpms from this link https://zdohnal.fedorapeople.org/.sane/ ? Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/8 ------------------------------------------------------------------------ On 2017-07-31T13:46:41+00:00 Zdenek wrote: Upstream accepted manpage patch as commit 56398ead607d8bcb9deef7ca3f4d7f78478f1b4c Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/9 ------------------------------------------------------------------------ On 2017-08-14T12:54:21+00:00 Zdenek wrote: Created attachment 1313099 Proposed patch Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/10 ------------------------------------------------------------------------ On 2017-08-14T12:58:25+00:00 Robert wrote: (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. Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/11 ------------------------------------------------------------------------ On 2017-08-14T12:59:18+00:00 Robert wrote: Do you still need a test for verification? Or do you have such hardware yourself around somewhere? Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/12 ------------------------------------------------------------------------ On 2017-08-14T13:03:31+00:00 Zdenek wrote: Yes, would you mind testing it? I do not have such HW unfortunately. Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/13 ------------------------------------------------------------------------ On 2018-04-10T13:47:21+00:00 errata-xmlrpc wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1741977/comments/16 ** Changed in: sane-backends (Fedora) Status: Unknown => Fix Released ** Changed in: sane-backends (Fedora) Importance: Unknown => High ** Bug watch added: alioth.debian.org/ #315792 http://alioth.debian.org/support/tracker.php?aid=315792 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1741977 Title: Scanning fails with many Samsung multifunctions (SCX-3200, SCX-3400, CLX-6260) after upgrading to Ubuntu 17.10/18.04 (SANE_USB_WORKAROUND=1 needed) Status in sane-backends package in Ubuntu: Confirmed Status in sane-backends package in Baltix: Triaged Status in sane-backends package in Fedora: Fix Released Bug description: Upgraded from kubuntu 17.04 to 17.10. Before the upgrade I was able to use my printer/scanner Samsung SCX-3200 without problems, with 17.10 I can only use the printer part. sane-find-scanner finds the scanner $ sane-find-scanner -q [...] product=0x3441 [SCX-3200 Series]) at libusb:003:019 [...] Scanning fails with many Samsung multifunctions (including SCX-3400, SCX-4624f, CLX-6260) after upgrading to Ubuntu 17.10/18.04 It seems the best solution for now is to add SANE_USB_WORKAROUND=1 line to /etc/environment: echo "SANE_USB_WORKAROUND=1" | sudo tee -a /etc/environment or to /etc/systemd/user.conf: echo "DefaultEnvironment=SANE_USB_WORKAROUND=1"|sudo tee -a /etc/systemd/user.conf For more info why SANE_USB_WORKAROUND=1 is needed look at http://www.sane-project.org release notes of 1.0.27: Note 3: The Linux USB3 workaround which was added in version 1.0.25 is now disabled by default. If you have difficulty using a scanner which previously worked, or intermittent scanner availability, try setting the new environment variable SANE_USB_WORKAROUND=1 before starting frontend. I found this info in comments of bug #1728012 and https://askubuntu.com/questions/966834/ubuntu-17-10-and-samsung-scx-4624f-scanner-not-working/966835 When I start scanimage the first time, it can talk to the scanner just fine: $ export SANE_DEBUG_XEROX_MFP=255 $ scanimage -L [sanei_debug] Setting debug level of xerox_mfp to 255. [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize != null [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffdf4d2e220, 0 [xerox_mfp] list_one_device: libusb:003:018 [xerox_mfp] usb_dev_open: open 0x55d2e393c5d0 [xerox_mfp] :: dev_command(INQUIRY[0x12], 70) [xerox_mfp] [70] a8 00 43 10 53 61 6d 73 75 6e 67 20 53 61 6d 73 75 6e 67 20 53 43 58 2d 33 32 30 30 20 53 65 72 69 65 73 20 19 33 84 2b 00 00 27 d8 00 00 36 d8 00 01 51 00 00 01 00 00 00 00 36 d8 00 00 36 d8 00 01 05 05 00... [xerox_mfp] dev_inquiry: found Samsung/Samsung SCX-3200 Series [xerox_mfp] usb_dev_close: closing dev 0x55d2e393c5d0 device `xerox_mfp:libusb:003:018' is a Samsung Samsung SCX-3200 Series multi-function peripheral When I start scanimage a second time it cannot talk to the scanner anymore: $ scanimage -L [sanei_debug] Setting debug level of xerox_mfp to 255. [xerox_mfp] sane_init: Xerox backend (build 13), version != null, authorize != null [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffe9ae18760, 0 [xerox_mfp] list_one_device: libusb:003:018 [xerox_mfp] usb_dev_open: open 0x56138cfa1870 [xerox_mfp] :: dev_command(INQUIRY[0x12], 70) [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O [xerox_mfp] dev_command: dev_request: Error during device I/O [xerox_mfp] usb_dev_close: closing dev 0x56138cfa1870 [xerox_mfp] list_one_device: dev_inquiry(libusb:003:018): Error during device I/O Unplugging the usb cable and plugging it back in allows scanimage to talk to the scanner once. After that it fails again. The USB cable is not a problem, as it worked with 16.10. I downloaded VueScan and it has not problems to repeatedly scan pages using the same hw, which also indicates that this is a sw and not a hw problem. And just to mention it again, printing also works fine using the same cable. And yes, I tried multiple USB ports. All exhibit the same behaviour. When I execute scanimage -L once and start VueScan afterwards, then VueScan also doesn't see the scanner anymore. After unplugging and replugging the UBS cable and restarting VueScan, it's able to scan again. Looks to me like sane doesn't know how to talk to the scanner anymore. It seems that something get's messed up during the first usb command, which prevents subsequent usb commands from succeeding. I just downloaded 16.04.3 LTS and booted it from a USB stick. I can confirm that the scanner still works with 16.04. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sane-utils 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 8 20:53:07 2018 InstallationDate: Installed on 2016-04-03 (645 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sane-backends UpgradeStatus: Upgraded to artful on 2018-01-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1741977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
