Samsung scanner not working 17.10

Asked by Jarno

Hi,
Since I upgraded ubuntu to 17.10 my scanner multifunction samsung CLX-3300 is not working but Printer is operational.
With 16.10 I used official samsung scanner uld_v1.00.36_00.91 without any problem.

Now SYSLOG at device power on
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.190624] usb 3-9: new high-speed USB device number 11 using xhci_hcd
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.331421] usb 3-9: New USB device found, idVendor=04e8, idProduct=3456
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.331424] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.331426] usb 3-9: Product: CLX-3300 Series
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.331428] usb 3-9: Manufacturer: Samsung Electronics Co., Ltd.
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.331429] usb 3-9: SerialNumber: Z76KB8GF7E00AKV
Oct 23 14:41:33 jarno-MS-7817 kernel: [16552.332664] usblp 3-9:1.1: usblp2: USB Bidirectional printer dev 11 if 1 alt 0 proto 2 vid 0x04E8 pid 0x3456

sudo sane-find-scanner -q
found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x3456 [CLX-3300 Series]) at libusb:003:011
found USB scanner (vendor=0x046d, product=0x08ad) at libusb:003:003
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error

 simple-scan -d
[+0,00s] DEBUG: simple-scan.vala:637: Starting Simple Scan 3.26.1, PID=8122
[+0,03s] CRITICAL: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
[+0,03s] CRITICAL: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
[+0,06s] DEBUG: app-window.vala:1714: Loading state from /home/jarno/.cache/simple-scan/state
[+0,06s] DEBUG: app-window.vala:1671: Restoring window to 568x183 pixels
[+0,06s] DEBUG: autosave-manager.vala:64: Loading autosave information
[+0,06s] DEBUG: autosave-manager.vala:259: Waiting to autosave...
[+0,09s] DEBUG: scanner.vala:1454: sane_init () -> SANE_STATUS_GOOD
[+0,09s] DEBUG: scanner.vala:1460: SANE version 1.0.27
[+0,09s] DEBUG: scanner.vala:1521: Requesting redetection of scan devices
[+0,09s] DEBUG: scanner.vala:806: Processing request
[+0,16s] DEBUG: autosave-manager.vala:281: Autosaving book information
[+0,29s] DEBUG: app-window.vala:1775: Saving state to /home/jarno/.cache/simple-scan/state
[+7,34s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,34s] DEBUG: scanner.vala:1521: Requesting redetection of scan devices
[+7,34s] DEBUG: scanner.vala:806: Processing request
[+7,44s] DEBUG: app-window.vala:1775: Saving state to /home/jarno/.cache/simple-scan/state
[+14,26s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+14,36s] DEBUG: app-window.vala:1775: Saving state to /home/jarno/.cache/simple-scan/state
[+34,52s] DEBUG: app-window.vala:1775: Saving state to /home/jarno/.cache/simple-scan/state
[+34,88s] DEBUG: app-window.vala:1775: Saving state to /home/jarno/.cache/simple-scan/state
[+69,60s] DEBUG: app-window.vala:1775: Saving state to /home/jarno/.cache/simple-scan/state
[+70,95s] DEBUG: simple-scan.vala:454: Requesting scan at 150 dpi from device '(null)'
[+70,95s] DEBUG: scanner.vala:1569: Scanner.scan ("(null)", dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=ScanType.SINGLE, paper_width=2100, paper_height=2970, brightness=0, contrast=0, delay=15ms)
[+70,95s] DEBUG: scanner.vala:806: Processing request
[+70,95s] WARNING: scanner.vala:841: No scan device available

sudo sane-find-scanner
found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x3456 [CLX-3300 Series]) at libusb:003:011
found USB scanner (vendor=0x046d, product=0x08ad) at libusb:003:003
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

 scanimage -L
device `xerox_mfp:libusb:003:011' is a Samsung CLX-3300 Series multi-function peripheral
BUT 30 seconds later
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).

Device seems to be well detected but not supported by sane .

Does anybody have an idea ?
regards

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Jarno
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

http://www.sane-project.org/cgi-bin/driver.pl?manu=samsung&model=&bus=any&v=&p=

https://ubuntuforums.org/showthread.php?t=2114121

Says:

echo "usb 0x04e8 0x3456" | sudo tee -a /etc/sane.d/xerox_mfp.conf > /dev/null

Then reboot to test

Revision history for this message
Jarno (yannick-jarno) said :
#2

I launched the cmd echo "usb 0x04e8 0x3456" | sudo tee -a /etc/sane.d/xerox_mfp.conf > /dev/null but in fact i had already modified this file like that :

# Samsung CLX-3300 Series
usb 0x04e8 0x3456

# Samsung scanner CLX-3300 Series
usb 0x046d 0x08ad

usb 0x046d 0x08ad

Revision history for this message
Jarno (yannick-jarno) said :
#3

One thing more.
Each time i launch simple scan , i get in syslog:
Oct 24 11:40:44 jarno-MS-7817 colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1
Oct 24 11:41:02 jarno-MS-7817 simple-scan: io/hpmud/pp.c 627: unable to read device-id ret=-1

Revision history for this message
Jarno (yannick-jarno) said :
#4

to work around the malfunction of 17.10 I installed an ubuntu 16.04 in virtualbox 5.2
it worked the first time very well .

Revision history for this message
Jarno (yannick-jarno) said :
#5

I configured other depository for samsung drivers ( deb http://www.bchemnet.com/suldr/ debian extra ).
Yesterday an update was applied suldr-driver2-1.00.36 and now scanner is reachable.
I can scan documents, there are still some bugs and i am sometimes obliged to restart simple-scan but this is a a very clear improvement.
So i consider the problem solved and wait for futures improvements .