SULDR Forums Supported Printers Printing Questions Scanning Questions General Questions Samsung Installer

Common Issues Specifically Related to Scanning

Before trying to troubleshoot scanning, please make sure you are using the latest version of the driver from the repository. For network-connected scanners, it is particularly important that the suld-network-* package be up to date. If you installed the driver manually, you are on your own; there are too many library conflicts for scanning to be reliable, and many problems specific to particular releases of the driver from Samsung (such as mixing 64-bit and 32-bit installations). The repository addresses most of them, and I won't provide details here on how to reconstruct all of them manually (that information is available in various locations on this website and in the provided links.

Solutions to scanning problems depend on how the scanner is connected (USB, network, or parallel) and specific details of where the communication breakdown is, so the approaches below are broken down accordingly. I also highly recommend that you ensure you can print to your printer before worrying about scanning; if you can't print, you are almost certainly going to be unable to scan, and most of the suggestions below assume you have already sorted out how to get printing working.

S0. HELP! I Updated the Packages and Now I Can't Scan!
S1. The Scanner of a Multifunction Printer Doesn't Work
S2. USB-connected Scanner Is Not Recognized by sane-find-scanner
S3. USB-connected Scanner Is Recognized by sane-find-scanner But Does Not Work
S4. Which Printer Models Work With Which Scanning Driver?
S5. USB-connected Scanner Is Inconsistent/Often Fails and I'm Using an Old Distribution
S6. Network-connected Scanner Is Not Recognized by netdiscovery (v3.00.xx to 4.01.xx)
S7. Parallel-connected Scanner Is Not Working
S8. My CJX-xxxx Printer Does Not Scan
S9. My Scanner Worked Until I Updated to Ubuntu 12.04
S10. Imagemanager Will Not Start
S11. Network-connected Scanner Is Not Working
S12. smfpnetdiscovery (driver2 v1.00.xx) Produces No Output

S0. HELP! I Updated the Packages and Now I Can't Scan!

On rare occassions, something may not go smoothly in an upgrade process. You can try uninstall all your packages from this repository and then reinstalling the ones you still need. Otherwise, post to the forums for help.

S1. The Scanner of a Multifunction Printer Doesn't Work

Make sure you have followed all the following steps, or no other fix will have any success: Once you have completed these steps, and if your scanner still does not work, proceed to the appropriate next question. In some cases, a different suld-driver-* versions may help, but testing this is not a strict requirement of proceeding to other solutions. Some scanners may only work with particular driver versions, although this is relatively rare.

S2. USB-connected Scanner Is Not Recognized by sane-find-scanner

If you enter "sane-find-scanner" in a terminal and do not get output indicating that your computer "sees" your scanner, you can try the following:

S3. USB-connected Scanner Is Recognized by sane-find-scanner But Does Not Work

If you enter "sane-find-scanner" in a terminal and do get output indicating that your computer "sees" your scanner, but xsane or "scanimage -L" or similar programs do not recognize the scanner, you can try the following:

S4. Which Printer Models Work With Which Scanning Driver?

Click here for supported models. Most supported USB models work through standard libsane libraries and utility varies with the libsane version; you can get updated information here and here if you search for "samsung". Some additional printers appear to be supported by foomatic to varying degrees. This is erratic, version-dependent, and sometimes breaks later. Additional support cannot easily be forced, but you can try the previous the answer to the previous question.

S5. USB-connected Scanner Is Inconsistent/Often Fails and I'm Using an Old Distribution

Occasionally and only in distributions released prior to 2008 (Debian 4.x (Etch), Ubuntu 7.10 (Feisty) and earlier), the USB support will be quirky or broken using these packages. I don't know why this is, but there isn't a good solution due to limitations in the way the Samsung drivers themselves work. Your best bet is to update your distribution. Most of the above solutions are only available with newer distribution releases. Although less common, distributions released prior to 2010 also are often best dealt with simply by updating the whole system, as several kernel versions between 2.6.33 and 3.0 seemed to have problems with CONFIG_USB_DEVICES="n" being set during compilation, but effects are highly erratic, and better work-arounds usually exist if you have more recent system libraries installed. One potentially useful approach that may still of interest is described here and with more details and a script here.

S6. Network-connected Scanner Is Not Recognized by netdiscovery (driver 3.00.xx to 4.01.xx)

First, make sure that you are using the most recent version of the suld-network-1 or suld-network-2 package. Second, run the following command in a terminal: "/opt/Samsung/mfp/bin/netdiscovery --all --scanner". If it reports a scanner found and the model matches yours, then you should be ready to go; if not, post to the forums. On the other hand, if 0 scanners are found (in recent versions, only the line "# DEBUG: Network printers discovery utility" will appear) or the model is incorrect, you need to consider the following:

S7. Parallel-connected Scanner Is Not Working

Good luck. I suggest updating to a newer model printer.

S8. My CJX-xxxx Printer Does Not Scan

I am not aware of any method for supporting this printer, but have very limited information.

S9. My Scanner Worked Until I Updated to Ubuntu 12.04

There appears to be some subtle conflict with some (many?) printers and the Qt4 libraries if you scan using the Configurator interface (or smfpscan directly). Until I have time to track down the actual problem and possibly identify a solution, a simple fix is to install suld-configurator-*-qt3 instead of the default suld-configurator-*-qt4. The interface isn't as pretty, but otherwise it works the same (and it works with scanning under Ubuntu 12.04).

S10. Imagemanager Will Not Start

Newer releases of the Qt4 Imagemanager must be given a valid image file as a command parameter when starting. After that it works fine. This will be observed in the suld-configurator-2-qt4 package but not in other versions.

S11. Network-connected Scanner Is Not Working

In some cases, network connected scanners using the Xerox MFP backend may benefit from replacing USB information in /etc/sane.d/xerox_mfp.conf with the IP address of the printer. See this post for the (little) available information. At least with driver2 versions, setting SANE_DEFAULT_DEVICE to 'smfp:net;xxx.xxx.xxx.xxx' where xxx.xxx.xxx.xxx is the IP address of your printer can solve problems with multiple network interfaces causing detection problems. See this post for additional information regarding setting up xerox_mfp.conf for some printers.

S12. smfpnetdiscovery (driver2 v1.00.xx) Produces No Output

This appears to be its normal mode. Unlike the older netdiscovery, smfpnetdiscovery does not seem to produce any human-readable output, whether or not the printer is detected.

Repository Information Legal Contact Alternative Drivers