I use Kubuntu 16.04 (KDE-Plasma 5.5.5 Qt 5.5.1) and have a HP Officejet 4500, connected via Ethernet and HPLIP, working as printer and scanner for years. For testing I use VirtualBox with Kubuntu 16.04 as gast so I can easily reset (snapshot) instead of un-install the driver. The HP works fine in VB. Now I purchased a new Samsung CLX-6260FW Printer/Scanner, connected via Ethernet-LAN. By entering the IP in Firefox, I have also access to the Samsung printer (SyncThru Web Service).
--- short version ---
With uld (from) hp.com, suld-driver2-1.00.39, suld-driver-4.01.17 with suld-configurator-2-qt4, suld-driver2-common-1 and suld-driver-common-1 the Samsung CLX-6260 is working as printer but not recognized (really) as scanner.
With suld-driver-4.01.17 and suld-configurator-1-qt4 it doesn't work neither as printer nor as scanner but is at least recognized as scanner
--- detailed version ---
First I installed the uld from hp.com - printer works fine (Ubuntu Printer Test Page says Driver CXL6260.ppd, V1.9) but gscan2pdf and Skanlite can't see the Samsung Scanner.
Than I found your site and installed "deb http://www.bchemnet.com/suldr/ debian extra". For my CLX-6260 the Minimum Version is 4.00.36 and 1.00.39 (driver2).
First I installed suld-driver2-1.00.39 because it is fresh. I used the Kubutu-system to add the printer driver CLX-6020 Series PS (en). The Ubuntu Printer Test Page says Driver CXL6260.ppd, V1.8. But gscan2pdf and Skanlite can't see the Samsung Scanner. I also added my user to group "saned" - no effect.
Than I installed suld-driver-4.01.17 and suld-configurator-2-qt4. The suld-configurator finds the pre-installed HP-4500. When I tried to add the Samsung printer, CLX-6260 Series on 10.0.2.2 is found in the network (configure opens file:///opt/Samsung/mfp/share/utils/SetIPApplet.html empty in the browser) but there is no driver in the list. Adding must be canceled. With Kubuntu system I could add CLX-6020 Series PS (en) and the test page was printed (Driver CXL6260.ppd, V1.3). If I look up the scanners, CLX-6260 Series on 10.0.2.2 is found but properties shows "Error during device I/O". gscan2pdf and Skanlite list the HP and the Samsung scanner but can't use the Samsung scanner. gscan2pdf says "Error opening device: opening device 'smfp:SAMSUNG CLX-6260 Series on 10.0.2.2': Error during device I/O". With suld-configurator-2-qt4-root it's the same. I also added my user to group "saned" - no effect.
Now I tried suld-driver-4.01.17 and suld-configurator-1-qt4. Now the Samsung Unified Driver Configurator can't find the pre-installed HP printer/scanner but I can add the Samsung CLX-6260 Series PS (en), Port: ipp://10.0.2.2. In the Kubuntu-system all HP and Samsung printers are listed. If I try to print a testpage with suld-configurator-1-qt4, it says "checkinig driver ... ok" and "printing test paqge ...ok" gut the Kubuntu-printer queue says Printer status could not be determined. The same happens if I use other programms for printing, e.g. kate. If I look up the scanners, CLX-6260 Series on 10.0.2.2 is found and properties open a window with big preview- and scan-buttons that says "unable to detect options for selected device". gscan2pdf and Skanlite list the HP and the Samsung scanner but can't use the Samsung scanner. gscan2pdf says "Error opening device: opening device 'smfp:SAMSUNG CLX-6260 Series on 10.0.2.2': Error during device I/O". With suld-configurator-1-qt4-root it's the same. I also added my user to group "saned" - no effect.
I also tried suld-driver2-common-1 and suld-driver-common-1, added user to "saned". In both cases the Ubuntu test page can be printed(Driver CXL6260.ppd, V1.3) but the Samsung scanner is not found.
What am I doing wrong?
Now I use suld-driver2-common-1. Yesterday I found this https://ubuntuforums.org/showthread.php?t=2227458&p=13039406#post13039406 and did sudo vi /etc/sane.d/xerox_mfp.conf:
#Samsung CLX-6260 Series
#usb 0x04e8 0x3455
Now the Scanner is recognized.
Yesterday scanning worked, until I used 600dpi. Today scanning doesn't work even at 100dpi. Skanlite is still waiting for the beginning of the scan process... Is there a chance, that this is, because I used the reset-button on the printer yesterday?