Samsung M2070W scanner no longer working in 17.10

Question

I own a Samsung M2070W printer/scanner, which worked in 17.04. After installing 17.10, it prints but is not detected my Simple Scan or Xsane.

The latest drivers from the Samsung website are installed.

It is detected by sane-find-scanner but not scanimage-L. Output from the former:

found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x3469 [M2070 Series]) at libusb:003:003

I tried modifying the .bashrc as suggested in Samsung SCX-4200 Scanner not working (printing OK) 14.04, but it didn't work.

I've seen this issue on several forums but no one seems to have a solution.

https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352 — , Oct 29 '17 at 16:21
Sorry, but I'm not tech-savvy enough to know what to do with that information? Does it mean the bug is now fixed? — Lolwhites, Oct 29 '17 at 19:57
it means that many people do have this problem and it is not fixed. somebody changed something, did not test it very well, and thousands of users cannot scan now. — , Oct 31 '17 at 09:45

score 24 · Answer 1 · edited Oct 08 '18 at 07:04

I just got the scanner from Samsung M2070FW running with Ubuntu 18.04. Just follow these steps:

Get UnifiedLinuxDriver-1.00.37.tar.gz from this site and unpack it, open a terminal and do:
```
cd /UnifiedLinuxDriver-1.00.37/uld
sudo ./install.sh
```
After successful installation of the Samsung Driver for the printer and the scanner, you can installer the printer first via Cups. For the scanner however, there should be a new directory with a single file in it:
```
/opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1
```
If you use a 64-bit system (which you probably do), use the terminal again to change to the scanner driver directory. Here you put a symbolic link to the file in /opt:
```
cd /usr/lib/x86_64-linux-gnu/sane
sudo ln -s /opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1 /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1
```
But things still didn't work, so I had to install a USB library:
```
sudo apt install libusb-0.1-4
```
After that, I made sure that I was in the same network with my printer (via ping) and did scanimage -L:
```
$ scanimage -L
device `smfp:net;192.168.1.20' is a Samsung M2070 Series on 192.168.1.20 Scanner
```

If pinging your scanner works but the command finds nothing, you can start to debug things:

cd
export SANE_DEBUG_DLL=255 && scanimage -L &> debug.txt
grep -n2 "libsane-smf" debug.txt

If everything works correctly, you would get the following output:

....
84-[dll] sane_get_devices
85-[dll] load: searching backend `smfp' in `/usr/lib/x86_64-linux-gnu/sane'
86:[dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1'
87:[dll] load: dlopen()ing `/usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1'
88-[dll] init: initializing backend `smfp'
89-[dll] init: backend `smfp' is version 1.0.1
....

If not, you might find a hint as to what file is missing or not found.

Did everything you described, and I get the same output as you do in step 5. The scanner works, after a fashion - Simple Scan does one page fine, but hangs on the second. However, it's fine if I run it in a terminal. — Lolwhites, Jun 28 '18 at 09:53
Hi. I have Lenovo B50 Laptop with Ubuntu 18.04 and Samsung Xpress M2070W. Your scanner stuff saved my day, Thank you. — Jacob, Sep 18 '18 at 14:28
18.04 and C480W - fix driver location and `sudo apt install libusb-0.1-4` did it for me. Thanks! — František Hartman, Jan 20 '19 at 18:46
Thank you so much! Also i can add that only SimpleScan app was able to actually do scanning - https://launchpad.net/simple-scan . Dunno why the reason of this — Xotabu4, Nov 14 '19 at 11:25
I used `UnifiedLinuxDriver-1.00.39.tar.gz` driver version and it worked on Ubuntu 18.04. — elomage, Mar 28 '20 at 12:47
Your process worked for me for USB with M2070 with Ubuntu Eoan 19.10. Thanks for posting — rupert160, Apr 06 '20 at 04:03

score 12 · Answer 2 · edited Oct 08 '18 at 07:01

12

See the bug report of this problem and the workaround that I posted in that bug report. Let me sum it up here to help you out:

Link the files libsane-smfp* in the sane folder found at /usr/lib/sane to the sane folder found at /usr/lib/x86_64-linux-gnu/sane.
```
sudo ln -sfr /usr/lib/sane/libsane-smfp* /usr/lib/x86_64-linux-gnu/sane
```
As root, edit the file 59-smfp_samsung.rules (you can find it in /etc/udev/rules.d) to include the following code/scanner number along with other Samsung model numbers which are already there:
```
ATTRS{idProduct}=="2070", ENV{libsane_matched}="yes"
```

Voila. It should work like a charm.

I believe this bug mostly affects network scanners. Except with minor variations in the name/model numbers of other scanners, this workaround should work for other network scanners too. Check the bug-report link for Brother, Epson, and Xerox scanners.

edited Oct 08 '18 at 07:01

Zanna

69,223
56
216
327

answered Nov 22 '17 at 15:24

Rajasekharan N.

171
4

1

I tried this solution but it wont work with my scanner over wifi. – Francisco V. Mar 16 '18 at 09:34
1

Thanks a lot for this solution. This made my Samsung SCX-3205W scanner connected over Wi-Fi work in Ubuntu 18.04. – Maxim Egorushkin May 04 '18 at 23:45
Following these 2 steps, I got my Samsung Xpress M2070 printer/scanner working on Ubuntu 18.04 again (connected via USB cable, no Wifi). – Dzhuneyt Mar 31 '19 at 14:13

score 9 · Answer 3 · edited Oct 08 '18 at 07:38

9

For network Samsung scanners, put your scanner's IP address and optionally port anywhere in the file /etc/sane.d/xerox_mfp.conf:

tcp host_address [port]

It worked with my C460, probably would work also with other scanners, check the respective sane config file and settings here:

edited Oct 08 '18 at 07:38

Zanna

69,223
56
216
327

answered Mar 17 '18 at 11:04

iipavlov

91
1
1

Mine is connected by USB. How do I find out the relevant information? – Lolwhites Mar 18 '18 at 18:47
Here is a good starting point for the usb configurationt: https://www.systutorials.com/docs/linux/man/5-sane-usb/ – iipavlov Mar 20 '18 at 01:35
that worked for me (without installing the Samsung driver), except that the printer/scanner is now waking up every time I start the system or plug in a USB device – Damien May 11 '18 at 21:42
Excellent, this worked for me with a Samsung SCX-3405FW wifi printer and scanner. and I'm on a new install of Ubuntu 18.04 – Julio Aug 03 '18 at 10:24
1

This worked for me for a M2070FW after a fresh Ubuntu 19.04 install. Note that the port for the scanner is 9400. If found that information here: https://bbs.archlinux.org/viewtopic.php?id=247495 – Bim Aug 28 '19 at 07:52

score 3 · Answer 4 · edited Oct 08 '18 at 07:32

3

For a Samsung Scanner/Printer M2885FW, which is connected over WiFi, and Ubuntu 18.04 a combination of two suggestions in this thread solved the problem with scanning: Rajasekharan N.'s answer and Jevgenij Evll's answer.

I rebuilt the links found at /usr/lib/sane in the folder /usr/lib/x86_64-linux-gnu/sane by using following lines:

sudo ln -s /opt/smfp-common/scanner/lib/libsane-smfp.so.1.0.1 /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1.0.1
sudo ln -s /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1.0.1 /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1
sudo ln -s /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so.1 /usr/lib/x86_64-linux-gnu/sane/libsane-smfp.so

After this step I un- and reinstalled the Samsung drivers.

edited Oct 08 '18 at 07:32

Zanna

69,223
56
216
327

answered May 07 '18 at 11:53

Marion Sr

31
6

Hi Marion! In your answer, can you include link(s) to the questions/answers that helped you? – Hee Jin May 07 '18 at 16:04
The scanner is now detected by both Xsane and Simple Scan. However when I try to actually scan, Xsane returns the message "Failed tro start scanner: Error during device I/O" while Simple Scan says "Failed to start scan". Running in a terminal provides no information. – Lolwhites May 08 '18 at 19:15
@Lolwhites. Have you tried to run xsane as a root to check if your problem could be a permission issue? – Marion Sr May 15 '18 at 11:42
I found that plugging the scanner directly into a USB port instead of via a hub solved many of the issues, but I can still can't scan multiple pages. – Lolwhites May 16 '18 at 14:55

score 3 · Answer 5 · edited Jul 19 '20 at 14:11

3

In Ubuntu 18.04 LTS I had to replace libusb-0.1.so.4 with libusb-dev The command for this task is:

sudo apt-get install libusb-dev

edited Jul 19 '20 at 14:11

Zanna

69,223
56
216
327

answered Jan 21 '19 at 17:39

Thomas Zahreddin

39
2

2

worked for me, Ubuntu 18.04, Samsung M2070W – Karolis Ryselis Feb 25 '19 at 16:31
I replaced libusb-0.1.so.4 with libusb-dev and now scanner works (`sudo apt-get install libusb-dev`). SAMSUNG m2070FW on Kubuntu 18.10 – Luigi Maria Pandolfi Feb 19 '19 at 08:43

score 1 · Answer 6 · answered Dec 19 '18 at 09:33

1

I have a Samsung M2070 printer/scanner, had the same problem as you, and I fixed the problem by uninstalling Ubuntu 18.04 and reinstalling Ubuntu 16.04.

answered Dec 19 '18 at 09:33

Jerry777

141
1
1
6

Farid Cheraghi · Answer 7 · 2019-08-23T21:24:59.967

I followed the instructions in https://www.bchemnet.com/suldr/ and it solved my problem.

I installed keyring package http://www.bchemnet.com/suldr/pool/debian/extra/su/suldr-keyring_2_all.deb using

dpkg -i suldr-keyring_2_all.deb

and after adding the following apt source,

sudo bash -c 'echo "deb https://www.bchemnet.com/suldr/ debian extra" >> /etc/apt/sources.list'

I installed suld-driver2-1.00.39 package:

sudo apt install suld-driver2-1.00.39

From then on, scanimage -L and "simple scan" worked fine.

score 0 · Answer 8 · edited Oct 08 '18 at 07:35

0

I tried Rajasekharan N.'s solution with Ubuntu 18.04 for Samsung 2070w and the newest uld driver downloaded from hp - scanner didn't work even connected via USB cable.

So

I removed the uld driver using the uninstall.sh provided with the uld driver
I reinstalled using the older Samsung uld driver (sadly I have no link for it) and it works again

edited Oct 08 '18 at 07:35

Zanna

69,223
56
216
327

answered Feb 21 '18 at 22:15

morkevicius

141
4

score 0 · Answer 9 · edited Nov 11 '17 at 17:50

0

For my SAMSUNG M2070 running uninstall-scanner.sh and then install-scanner.sh again (with restarting afterwards) fixed the issue. I also installed libsane and sane-utils from the proposed updates repo prior to the above, but not sure if this step is needed.

edited Nov 11 '17 at 17:50

David Foerster

35,754
55
92
145

answered Nov 11 '17 at 17:21

Jevgenij Evll

109
2

1

Uninstalling and reinstalling the driver didn't fix teh issue. I tries to get the latest version of sane via the ppa rolfbensch/sane-git androlfbensch/sane-release but the upgrade is held back. – Lolwhites Nov 12 '17 at 19:51
Use the official aartful-proposed repo for getting the newer sane version (you can enable this repo in settings). – Jevgenij Evll Nov 13 '17 at 09:31
I removed the ppa and enabled the repo but the upgrade was still held back. I ran apt install libsane-common libsane-dev sane-utils and it worked, but now running Simple Scan causes a segfault and other programs like Xsane won't install because of dependency issues. – Lolwhites Nov 16 '17 at 16:08
You don't need to install lisane-dev, but you need to install libsane1 from the experimental repo. – Jevgenij Evll Nov 17 '17 at 08:43
Actually, the latest libsane version has been released to updates 2 days ago, so you might get it from your regular repo. – Jevgenij Evll Nov 17 '17 at 08:46
I can't install libsane1 (on which Simple Scan depends) as it says: Depends: libsane-common (= 1.0.27-1~experimental2ubuntu2.1). Trying to install ibsane-common produces the message : libsane-common is already the newest version (1.0.27-artful1) The aartful-proposed repo is enable in Software Sources. – Lolwhites Nov 18 '17 at 20:08
Like I wrote, the regular updates repo got the new versions already, so you can try uninstalling all experimental stuff, disabling the experimental repo and reinstalling from your regular repo – Jevgenij Evll Nov 20 '17 at 08:33
I had pretty much given up on this as attempting to resolve the dependencies led to the system uninstalling things that I needed more, like gnome-control-center. Trouble was I couldn't figure out what I needed to undo. Any idea what I should try uninstalling an reinstalling after disabling the experimental repo? – Lolwhites Feb 24 '18 at 20:32
Have freshly installed 18.04 but the issue persists. The scanner is detected by sane-find-scanner but not scanimage -L: found USB scanner (vendor=0x04e8 [Samsung Electronics Co., Ltd.], product=0x3469 [M2070 Series]) at libusb:002:002 – Lolwhites Apr 27 '18 at 08:44

Samsung M2070W scanner no longer working in 17.10

9 Answers9

Linked

Related