FS#33982 - Supported Samsung MFP scanner fails to work - possible upstream sane-backends bug
Attached to Project:
Arch Linux
Opened by Mike Cloaked (mcloaked) - Saturday, 23 February 2013, 21:34 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 06 May 2013, 17:53 GMT
Opened by Mike Cloaked (mcloaked) - Saturday, 23 February 2013, 21:34 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 06 May 2013, 17:53 GMT
|
Details
Description:
Samsung MFP SCX-4500W is in the list of supported scanners for sane-backends. Plugging in the scanner via usb it is detected by the system but sane-find-scanner -v -v indicates a problem since the chipset is not detected (see attached file). The scanner then fails to work via xsane. scanimage -L does give a "normal looking" information line the first time it is executed, but then fails if the same command is executed a second time. $ scanimage -L device `xerox_mfp:libusb:001:006' is a Samsung Samsung SCX-4500W Series multi-function peripheral But if I do it again then: scanimage -L 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). I tried to add a line to 75-sane.rules in /etc/udev/rules.d/ with: ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="342b", MODE="0660", GROUP="scanner", ENV{libsane_matched}="yes" This gave no change to the symptoms. My username is a member of both lp and scanner groups. The lines in messages.log are for example: Feb 22 19:39:26 localhost kernel: [32142.463787] usblp 3-4:1.1: usblp0: USB Bidirectional print r dev 8 if 1 alt 0 proto 2 vid 0x04E8 pid 0x342B Feb 22 19:39:26 localhost colord: Device added: sysfs-Samsung_Electronics_Co.__Ltd.-SCX-4500W_Series Feb 22 19:39:26 localhost systemd[1]: Starting Printer. Feb 22 19:39:26 localhost systemd[1]: Reached target Printer. Feb 22 19:39:26 localhost systemd[1]: Starting Configure Plugged-In Printer... Feb 22 19:39:27 localhost systemd[1]: Started Configure Plugged-In Printer. Feb 22 19:39:27 localhost systemd[1]: configure-printer@usb-003-008.service: main process exited, code=exited, status=1/FAILURE Feb 22 19:39:27 localhost systemd[1]: Unit configure-printer@usb-003-008.service entered failed state This is for a fully updated x86_64 bit system. There seems to be a possibly related upstream bug at: https://alioth.debian.org/tracker/index.php?func=detail&aid=314021&group_id=30186&atid=410366 The above report is for a different hardware device but may be connected? Additional info: * package version(s) extra/sane 1.0.23-2 [installed] * config and/or log files etc. See attached sane-find-scanner -v -v output file. Steps to reproduce: Plug in MFP - type the commands suggested above. Attempt to run xsane - code hangs and no scanning is done - scanner hardware makes no response to preview scan despite being "detected" by sane-find-scanner. (Note that separately the printer functions are working fine once the appropriate udev rule is added to the rules file - and it is only the scanner that fails to work despite working normally when plugged into a Fedora 16 system running an older version of sane-backends until it was disconnected when the machine was re-installed with arch linux x86_64) 
sane-find-scanner-v-v.txt
(0 KiB)
|
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Monday, 06 May 2013, 17:53 GMT
Reason for closing: Upstream
Additional comments about closing: Please use forums for support request. Re-open or open a bug report here, if package bug is found or open a ticket on upstream in case of problem.
Monday, 06 May 2013, 17:53 GMT
Reason for closing: Upstream
Additional comments about closing: Please use forums for support request. Re-open or open a bug report here, if package bug is found or open a ticket on upstream in case of problem.
Here is the result of doing what you suggested:
[root@home1 ~]# rmmod usblp
[root@home1 ~]# scanimage -L
device `xerox_mfp:libusb:003:004' is a Samsung Samsung SCX-4500W Series multi-function peripheral
[root@home1 ~]# scanimage -L
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).
So that does not help.
I have an older laptop with arch installed which is i386. The following procedure was used to test this possible issue:
1) With the scx-4500W switched on and connected the main arch server running x86_64 but on this machine does not scan, I disconnected the usb connector.
2) With the laptop booted up, plugged the usb connector in to the laptop (laptop is running arch i386)
3) Start xsane on the laptop.
4) Scanning works perfectly with no problems at all.
5) Plug the scx-4500W back into the x86_64 machine - and start xsane. Try to scan - xsane hangs. Have to kill the xsane process.
This seems to confirm that there is a problem with only x86_64!
I plugged the scx4500w into a laptop running x86_64 arch and the scanner works perfectly - so it is not a 32 bit vs 64 bit issue at all! It is also not a problem with the scanner or the sane package but something specific with the main machine that I connect it to.
It just does not work on the main machine that I had the problem with but works fine on all the other machines that I have plugged the same scanner into!
I am now completely foxed as to how to get some diagnostics that might progress this problem? If anyone can suggest how I can get a backtrace or some diagnostics I would very much appreciate it.
Thanks.