I don't understand why Linux USB3 workaround which was added in version 1.0.25 is disabled by default in SANE 1.0.27 :( Maybe Ubuntu developers should patch SANE to enable SANE_USB_WORKAROUND=1 by default on all computers with USB 3.x ports? Anyone knows if SANE_USB_WORKAROUND=1 variable could cause any problems? If not, then why don't set this by default?
-- 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: Unknown 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
