- Welcome to Samsung Unified Linux Driver Repository Forum.
| SULDR | Forums | Supported Printers | Printing Questions | Scanning Questions | General Questions | Samsung Installer |
Recent posts
#11
Using the Repository / Re: Debian apt-get policy will...
Last post by bchemnet - May 10, 2025, 08:09:20Quote from: adubourg on May 10, 2025, 01:07:36Thanks for the quick response!
But is it really necessary to leave the old key, since repository users will automatically update to the new keyring package by merely using the repository?
Yes, the old key has to remain for a while. The key is used to sign the information about available packages, which is read before updates happen. If the existing key on someone's system does not match the signature, the update to the new key will not be allowed automatically. So I have to temporarily sign the package list with both keys, so that everyone can update without having to manually install the new key. And many people do not run updates every day, so it can take a while before the large majority of users have installed the new key.
The reason revoking the old key does not help is that the warning is not actually about the key. It is a warning about the signature in the package file, which still refers to the old key whether or not the key is trusted by your system. I am not familiar enough with Sequioa (the new PGP system replacing GPG in Debian) to know if there is a way to suppress the warning during this transition. If the package sqv is not installed (and gpg still is), there is no warning, although that is not an elegant solution or consistent with the direction Debian is moving in.
#12
Using the Repository / Re: Debian apt-get policy will...
Last post by adubourg - May 10, 2025, 01:07:36Thanks for the quick response!
But is it really necessary to leave the old key, since repository users will automatically update to the new keyring package by merely using the repository?
[EDIT] I've tried removing the old key from '/etc/apt/trusted.gpg.d/suldr-keyring.gpg', so that now it only contains
but I still have the same warning from `apt-get update`... However, it might just be because I don't really know what I'm doing with GPG >_<'
-- Alex
But is it really necessary to leave the old key, since repository users will automatically update to the new keyring package by merely using the repository?
[EDIT] I've tried removing the old key from '/etc/apt/trusted.gpg.d/suldr-keyring.gpg', so that now it only contains
pub ed25519 2025-05-09 [SC] [expires: 2035-05-07]
31712967E9DA399C42BED2F5A890B7701F3014B7
uid bchemnet <suldr@bchemnet.com>
sub cv25519 2025-05-09 [E] [expires: 2035-05-07]
but I still have the same warning from `apt-get update`... However, it might just be because I don't really know what I'm doing with GPG >_<'
-- Alex
#13
Using the Repository / Re: Debian apt-get policy will...
Last post by bchemnet - May 09, 2025, 18:50:41Thanks for the alert. Apparently the key was one caught in a long-standing bug that is now being exposed as Debian changes over their default GPG tool. I have added a new key that does not trigger the warning. You may still see the warning for the existing key until I remove it, but I will allow a few months before doing so to give repository users time to update to the new keyring package.
#14
Using the Repository / Debian apt-get policy will rej...
Last post by adubourg - May 08, 2025, 11:36:58Hi,
:(
-- Alex
I just had a warning from `apt-get update` while updating my Debian system:
W: http://www.bchemnet.com/suldr/dists/debian/InRelease: Policy will reject signature within a year, see --audit for details
A: http://www.bchemnet.com/suldr/dists/debian/InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is:
Signing key on 230890002EDEE9679DE6FC73FB510D557CC3E840 is not bound:
No binding signature at time 2023-10-09T03:00:11Z
because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance
because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
:(
-- Alex
#15
Scanning / Re: Scanning with CLX-2160
Last post by bchemnet - August 27, 2024, 19:58:22Thank you for sharing this fix.
#16
Scanning / Scanning with CLX-2160
Last post by crupf - August 27, 2024, 02:50:43With above MFP I got the error that no paper is found in document feeder (error message was German, I don't know the exact wording in English). I got it working by changing the definition for the printer CLX-2160 in "/etc/sane.d/smfp.conf". I guess that this change is helping in order to tell the driver that the scanner has no ADF and it is not required to wait for paper there...
<model vendor="samsung" id="clx216x" modelstring="CLX-216x Series" type="usb">
<hwoption name="twainspec" type="enum">2</hwoption>
<hwoption name="sleep_after_scan_ms" type="int">0</hwoption>
<hwoption name="adf" type="enum">no</hwoption>
<hwoption name="flatbed" type="enum">yes</hwoption>
<hwoption name="resolution" type="list" default="150">75 150 200</hwoption>
<hwoption name="colorcompose" type="list" default="gray256">gray256 bw_halftone bw_lineart</hwoption>
<hwoption name="pageformat" type="list" default="a4">
a4 letter legal statement folio
a5 a5_extra b5 b5_extra b5_jis
executive quatro letter_plus a4_plus
envelope_9 envelope_10 envelope_11 envelope_12
envelope_14 envelope_b5 envelope_b6 envelope_c5
envelope_c6 envelope_c6c5 envelope_dl
envelope_110x230 envelope_monarch
custom
</hwoption>
</model>
<model vendor="samsung" id="clx216x" modelstring="CLX-216x Series" type="usb">
<hwoption name="twainspec" type="enum">2</hwoption>
<hwoption name="sleep_after_scan_ms" type="int">0</hwoption>
<hwoption name="adf" type="enum">no</hwoption>
<hwoption name="flatbed" type="enum">yes</hwoption>
<hwoption name="resolution" type="list" default="150">75 150 200</hwoption>
<hwoption name="colorcompose" type="list" default="gray256">gray256 bw_halftone bw_lineart</hwoption>
<hwoption name="pageformat" type="list" default="a4">
a4 letter legal statement folio
a5 a5_extra b5 b5_extra b5_jis
executive quatro letter_plus a4_plus
envelope_9 envelope_10 envelope_11 envelope_12
envelope_14 envelope_b5 envelope_b6 envelope_c5
envelope_c6 envelope_c6c5 envelope_dl
envelope_110x230 envelope_monarch
custom
</hwoption>
</model>
#17
Using the Repository / Re: Quick Guide to Setting Up ...
Last post by bchemnet - June 29, 2024, 07:42:14Update: there is no reason to keep the repository enabled on your system after installing the desired packages, as there are unlikely to be any future updates. See this announcement:
https://www.bchemnet.com/suldr/forum/index.php?topic=406.0
https://www.bchemnet.com/suldr/forum/index.php?topic=406.0
#18
Announcements / Samsung printer drivers will n...
Last post by bchemnet - June 29, 2024, 07:40:22Summary: starting in a year or two, the vast majority of Samsung-branded printers will no longer be able to print when using a version of Linux incorporating CUPS 3.0 or higher.
When CUPS 3.0 is released, printer drivers will no longer function. The only printing methods supported by CUPS will be driverless options listed here:
https://openprinting.github.io/driverless/
Most Samsung printers do not support any of these options (although some later models do apparently work with IPP, possibly with a reduced feature set). While the CUPS team has provided a limited mechanism for driver-mandatory printers to still function the 3.0 series, that mechanism is not applicable to the Samsung driver. The CUPS team has effectively declared that these older printers are simply to not be supported. I do not have any information to help you determine if your printer is an impacted one or not, other than to suggest that you try installing it using IPP instead of the driver (which can be done with existing CUPS versions) and see if it works.
As of May 2024, the planned release of CUPS 3.0 is "mid-2025". It has been pushed back several times already, so it may be later. And your particular distro may not incorporate CUPS 3.0 until significantly later still. But once 3.0 is on your system, the Samsung (or HP version) drivers will cease to function.
Note that all the packages will still be installable, as I have no plan to make them explicitly conflict with CUPS 3.0, and I will continue to provide the Samsung installers as well. There are two reasons for that: (1) the scanning functions of the drivers will still likely be useful to some people even when the printing drivers do not work, and (2) I do not want to cripple any possibility of a future work-around that allows these drivers to continue working, though I view that as extremely unlikely.
Use of this repository has slowly been declining since Samsung sold off their printer business, and HP sold only a couple of models that used the same driver system. I anticipate a significantly greater rate of decline over the next few years, but I intend to leave this resource in place as long as there are a significant number of people apparently benefitting from its availability.
At this time, I do not anticipate any future updates to the packages or content. Therefore, there is no reason to leave the repository enabled on computers once the desired packages have been installed.
Update February 2026 CUPS 3.0 is rolling out. I strongly recommend starting to move to Splix (see below) if possible.
When CUPS 3.0 is released, printer drivers will no longer function. The only printing methods supported by CUPS will be driverless options listed here:
https://openprinting.github.io/driverless/
Most Samsung printers do not support any of these options (although some later models do apparently work with IPP, possibly with a reduced feature set). While the CUPS team has provided a limited mechanism for driver-mandatory printers to still function the 3.0 series, that mechanism is not applicable to the Samsung driver. The CUPS team has effectively declared that these older printers are simply to not be supported. I do not have any information to help you determine if your printer is an impacted one or not, other than to suggest that you try installing it using IPP instead of the driver (which can be done with existing CUPS versions) and see if it works.
As of May 2024, the planned release of CUPS 3.0 is "mid-2025". It has been pushed back several times already, so it may be later. And your particular distro may not incorporate CUPS 3.0 until significantly later still. But once 3.0 is on your system, the Samsung (or HP version) drivers will cease to function.
Note that all the packages will still be installable, as I have no plan to make them explicitly conflict with CUPS 3.0, and I will continue to provide the Samsung installers as well. There are two reasons for that: (1) the scanning functions of the drivers will still likely be useful to some people even when the printing drivers do not work, and (2) I do not want to cripple any possibility of a future work-around that allows these drivers to continue working, though I view that as extremely unlikely.
Use of this repository has slowly been declining since Samsung sold off their printer business, and HP sold only a couple of models that used the same driver system. I anticipate a significantly greater rate of decline over the next few years, but I intend to leave this resource in place as long as there are a significant number of people apparently benefitting from its availability.
At this time, I do not anticipate any future updates to the packages or content. Therefore, there is no reason to leave the repository enabled on computers once the desired packages have been installed.
Update February 2026 CUPS 3.0 is rolling out. I strongly recommend starting to move to Splix (see below) if possible.
#19
Printing / Re: Howto enable SULD drivers ...
Last post by chivi - May 12, 2024, 07:57:29To my regret arm64 cups filter from 1.00.39hp driver release does not work with Xerox_Phaser_3260:
But:
In the list of active CUPS jobs waiting for processing I observe this state:
For me amd64 userland QEMU emulation remains the only working solution.
Code Select
root@dietvm:/tmp/uld# ./install-printer.sh
**** Running install ...
**** Press 'Enter' to continue or 'q' and then 'Enter' to quit. :
...
**** Do you agree ? [y/n] : y
**** Are you going to use network devices ? If yes, it is recommended to configure your firewall.
**** If you want to configure firewall automatically, enter 'y' or just press 'Enter'. To skip, enter 'n'. : n
**** Registering CUPS backend ...
**** CUPS restart OK.
**** Print driver has been installed successfully.
**** Install finished.
But:
Code Select
==> /var/log/cups/access_log <==
192.168.1.3 - - [12/May/2024:14:19:06 +0200] "POST /printers/Xerox_Phaser_3260 HTTP/1.1" 200 491 Validate-Job successful-ok
192.168.1.3 - - [12/May/2024:14:19:06 +0200] "POST /printers/Xerox_Phaser_3260 HTTP/1.1" 200 1732960 Print-Job successful-ok
==> /var/log/cups/error_log <==
E [12/May/2024:14:19:08 +0200] [Job 1] Unable to open raster stream - : Broken pipe
In the list of active CUPS jobs waiting for processing I observe this state:
Quoteprocessing since Sun May 12 14:19:07 2024 "Filter failed"
For me amd64 userland QEMU emulation remains the only working solution.
#20
Scanner Server (Scan to PC) / Re: scan2pc.sh bash script
Last post by futurecrew - January 06, 2024, 02:32:34I was successful with your scan2pc.sh script for a Samsung SL-C472W model which has flat-bed scanner. Thank you. I tested at the environment of ubuntu 22.04 docker container with the suldr-driver2 and the packages you mentioned installed.
One thing I would like to comment about your script is that it won't work due to the imagemagick's pdf security policy problem. So in order to work properly just one line in the script needs to be modified like below.
--- scanimage $Verbose -d 'smfp:net;'$SCANNER_IP --resolution $DPI --page-format $ScanSize --format jpeg |
convert $COLOR - "$FileName"
+++ scanimage $Verbose -d 'smfp:net;'$SCANNER_IP --resolution $DPI --page-format $ScanSize --format ${FileType,,[A-Z]} --output-file "$FileName"
One thing I would like to comment about your script is that it won't work due to the imagemagick's pdf security policy problem. So in order to work properly just one line in the script needs to be modified like below.
--- scanimage $Verbose -d 'smfp:net;'$SCANNER_IP --resolution $DPI --page-format $ScanSize --format jpeg |
convert $COLOR - "$FileName"
+++ scanimage $Verbose -d 'smfp:net;'$SCANNER_IP --resolution $DPI --page-format $ScanSize --format ${FileType,,[A-Z]} --output-file "$FileName"
| Repository Information | Legal | Contact | Alternative Drivers |