Recent posts

#1

Announcements / Re: Samsung printer drivers wi...

Last post by bchemnet - February 24, 2026, 22:52:36

Open-source SpliX drivers now support the majority of SPL-based Samsung, Xerox and HP models.

Thanks for highlighting this.  I have updated the sticky post, as well as the web pages, to encourage moving to Splix as CUPS 3.0 rolls out.

#2

Printing / Re: Howto enable SULD drivers ...

Last post by ValdikSS - February 24, 2026, 15:59:30

For anyone interested, the latest git master of SpliX should now support essentially all Samsung, Xerox and HP SPL models.
https://github.com/OpenPrinting/splix/

Scanning via open-source xerox_mfp driver in SANE should also be supported, although you'll likely need to add your printer's USB VID/PID to /etc/sane.d/xerox_mfp.conf if it's not detected automatically.

#3

Announcements / Re: Samsung printer drivers wi...

Last post by ValdikSS - February 23, 2026, 18:34:06

Open-source SpliX drivers now support the majority of SPL-based Samsung, Xerox and HP models.
This driver is included in ghostscript-printer-app, which is designed to retain compatibility with CUPS 3.

Right now however (Feb 2026), ghostscript-printer-app has an outdated version of SpliX, but it's just a matter of changing the repository URL inside the build script and will be done eventually.

SpliX has recently received support for:

• HP Laser 107/135/136
• Samsung SL-M2020, M2070, ML-1670, ML-1860
• Samsung M262x 282x Series/M267x 287x Series/M283x Series
• Xerox Phaser 3020/3052/3260
• Xerox WorkCentre 3025/3215/3225

#4

Printing / SpliX supports HP Laser 107/13...

Last post by ValdikSS - February 20, 2026, 16:59:40

Just FYI that open-source SpliX driver supports all these previously unsupported printers in git master.
https://github.com/OpenPrinting/splix/tree/master

Xerox Phaser 3020 and WorkCentre 3025 code is available in xerox-3020 branch.
If anyone willing to test it, please report back, I'll merge it into master and make a release.
https://github.com/OpenPrinting/splix/tree/xerox-3020

#5

Announcements / Repository key and libxml2

Last post by bchemnet - November 28, 2025, 10:33:00

The repository key has been updated, with the old key removed.  A transition package was in place for six months, but if you missed that window and now get errors, refer to step 4 installing the repository (the part about the key) here: https://www.bchemnet.com/suldr/

Also, libxml2 is a required dependency of all versions of the driver, but has recently been removed from Debian Testing and will not be provided in future stable releases (and therefore will be dropped from Ubuntu, Mint, etc. that use Debian as the primary source of packages).  To ensure that the packages remain installable, I am now providing the most recent (as of today) version of the package through this repository.  The package is officially obsolete so no future updates are likely.

#6

General Discussion / Re: Please upgrade package dep...

Last post by bchemnet - October 18, 2025, 09:29:58

The dependencies have not been updated because the GUIs do not work with new versions.  The last update to the GUI from Samsung was over a decade ago, and the issue is worse than just python 2.7 dependency: it also requires Qt4, which is similarly obsolete and removed from Debian, and the GUI depends on a library with a known major, unpatched security flaw.  I have tested the programs with updated Qt and python, and they load but ultimately fail to work correctly.

I would like to achieve the goal that you describe, especially because I have seen a large increase in traffic to this repository over the past few months so there clearly is still interest in using these printers.  But the software is simply too old and closed source, so I do not have a solution.

The scantopc scripts could be updated, but would require a major rewrite because the core python library used was not ported to python 3.  So far nobody has been motivated to put in that effort since the original authors moved on.

The other problem that is coming up soon is CUPS 3.  When that is finally released, likely within the next year (although it has been "within a year" for nearly 4 years now), the drivers will also stop working due to a fundamental change in how CUPS will interact with printers.  Obviously it will take some time for CUPS 3 to work its way into enough distributions to have a major impact, but there is a definite end of life coming for the Samsung printers even if the hardware is still good, except for people with the considerable expertise to configure their printer without any GUI or CUPS.

#7

General Discussion / Please upgrade package depende...

Last post by Krotow - October 17, 2025, 06:13:22

Just installed SULDR driver for work with Samsung C460W printer from Linux Mint 22.2. That went fine. However all GUI package and some other package install fail with unmet dependencies to python 2.7 error

Code Select Expand

$ sudo apt install suld-scantopc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 suld-scantopc : Depends: python (>= 2.7) but it is not installable
                 Depends: python (< 3.0) but it is not installable
                 Depends: python-imaging-sane (>= 1.1.7) but it is not installable or
                          python-sane (>= 1.1.7) but it is not installable
                 Depends: python-pypdf (>= 1.13) but it is not installable
                 Depends: python-pysnmp4 but it is not installable
                 Depends: python-six but it is not installable

This obviously happen because Debian removed Python 2.x support 3 years ago. However it would be time to finally upgrade SULDR package dependencies too. Because Python 2.x was obsoleted eons ago. And most importantly, due to latest Microsoft Windows 11 shenanigans we can expect large user influx in Linux desktop realm. These people has SULDR compatible Samsung/HP printers as well. If supplies are available, printers usually outlive 3+ OS generations. Would be nice to not break user experience impression for newcomers.

#8

Scanning / Re: Samsung M2675FN no scan vi...

Last post by bchemnet - June 27, 2025, 21:10:22

Have you tried the various strategies given on the scanning page (https://www.bchemnet.com/suldr/scanning.html), specifically issue 11?

Unfortunately that collection of posts is probably all the specific guidance that I can provide.

#9

Scanning / Samsung M2675FN no scan via ne...

Last post by unmute - June 27, 2025, 09:11:05

Samsung Xpress M2675FN
Manjaro Linux Linux 6.12.34-1-MANJARO (x86_64)
Printer is Network connected via CUPS and ipp
Samsung unified driver 1.00.39-11, installed from AUR Repo
Cannot connect to Scanner. USB-port is dead. Setup via Network is mandatory. Printing is OK.

I could print and scan via network without any problems. Then a flash hit my computer and I am just installing a ne one. While that, I found, that the USB port of the printer is damaged also, so that I can access the printer only by network via CUPS and the Samsung driver integrated in CUPS.

Then I assumed, that I could get the scan function only by installing the samsung-unified-driver from AUR repo (I am on Manjaro / Arch-Linux) and in conjunction with an usb-port.

Luckily I have a second printer and same model with USB port working. I installed and I could scan with this second printer.

Then I returned to the printer with dead USB port, hoping, I now could scan via network, as the drivers are initialized correctly. But nope! – Everything was like before: I can print via network but cannot scan.

Due to other issues, I cannot use the other printer and connect via usb.

How can I manage to achieve scanning via network???

#10

Using the Repository / Re: Debian apt-get policy will...

Last post by bchemnet - May 13, 2025, 08:41:36

Another solution for anyone encountering this and wanting to prevent the warnings: disable this repository except when you are actively using it.  Given that the binary files are unlikely to ever change again, there really is no need to regularly check for updates after setting up working drivers, except possibly around the major updates of your Linux distro.  For context, there has not been an update to most driver packages in over 4 years, and it is entirely possible that there will never be another major change to most of them.