Messages

Thanks for sharing the solution.  Your error log seems to have not have had anything obvious in it, but clearly the job was being lost somewhere.  Fortunately that sounds like it is no longer a problem.

I suggest trying this (all will require sudo/root):
1. edit in /etc/cups/cupsd.conf to change the "LogLevel" line to "debug" instead of "warn"
2. restart the cups service
3. see what you get in /var/log/cups/error_log after a job that disappears without printing

Then post the error log output, if you cannot make progress yourself from what it says.

Just a thought: have you tried a different USB cable?  Very occasionally a cable will start to fail and cause connect/disconnect cycles such as this.

Unfortunately I do not have any hardware I can use to provide further insight, but perhaps someone else does and will.

Thanks for sharing.  I have added a link on the main pages to this post as an alternative driver option.

Whichever driver version you are using, I first recommend trying a different one.  This printer is supported by a wide range of options, and that may solve the problem.

If not, this sounds like an issue with CUPS.  The latest versions of CUPS are much slower under some circumstances and with some printers (brand-independent), but I have not worked out when or why.

The forum has undergone a major upgrade.  If you run into technical issues that seem related, let me know.

You are welcome.  I am glad it helped to keep old hardware working.

There is no development on any part of this project.  The Qt interface development was actually discontinued 9 years ago, well before Samsung sold their printer business to HP in 2016.  HP has not shown any interest in developing the driver (the last true update was nearly 6 years ago), let alone reviving that interface.  And there is no practical way to get Qt4 working in the latest Debian-based distributions due to some severe security issues that were discovered after Qt4 development ended.

However, you should be able to use system-config-printer to set up the printer.

I think you have two options.  One is to follow this thread, but use one of the version 3.xx drivers that support that printer instead of the latest package:
https://www.bchemnet.com/suldr/forum/index.php?topic=386.0

The other option is to set the printer to be a "generic postscript" as the printer type.  I seem to recall that works okay with that model, although not quite as well as the dedicated driver.

I have no way of testing or improving this, but will pin the thread so it is easily discoverable.

This feature may just be lost now.  I never provided the Printer Settings utility because it was separate from the driver, and it seems that Samsung had pretty much dropped it before selling their business to HP.  HP has completely dropped everything except the latest driver, which never worked with that utility.  So neither HP or Samsung is providing the Printer Settings utility either.  It is possible that you may be able to find a copy of the utility somewhere on the web, but you will have to dig fairly deep to find it.

Presumably the Windows driver or software still provides some way to do this.  Other than that, I do not have any solution for you.

I cannot your answer you question about M_PDF, but perhaps someone else will respond.

That said, even a limited function script may be of interest, so I encourage you to share what you have.  You might want to do so in a new thread, though.

suld-driver2-1.00.39:i386 : Depends: libxml2:i386 but it is not going to be installed
                             Depends: libstdc++6:i386 but it is not going to be installed
                             Depends: libusb-0.1-4:i386 but it is not going to be installed
                             Depends: libcupsimage2:i386 but it is not going to be installed

Those are all standard Debian packages, so perhaps you do not have the Debian main repository enabled, or the equivalent for a different distribution?  It is the universe repository for Ubuntu and derivatives, but I'm not sure how Raspberry-specific distributions are configured.

Is it possible that @markosjal and @schluppschlupp are encountering these problems because they are using a 32 bit Raspberry Pi OS?

Although I do not have any device to test with it, I believe the process should work with 32 bit as well.  Try replacing "amd64" with "i386" everywhere it appears.

Perhaps you do not have the Ubuntu "universe" repository active.  The last time I used Ubuntu (many years ago) that repository was active by default, but it seems that changed at some point.

Try

Code Select Expand


sudo add-apt-repository universe
sudo apt update


or see if you have the "community" (universe) repository active under your Software & Updates settings.

Then try installing the driver package again.

Now you should be able to do:

Code Select Expand


sudo apt update
sudo apt install suld-driver2-1.00.39


Probably you will be all set at this point.  But if not, delete & reinstall the printer.

Make sure your current terminal directory is the same as where you downloaded.  You might need to

Code Select Expand


cd ~/Downloads

or similar to depending on where your downloads are saved, before trying the dpkg command.

You need to install the suldr-keyring package first to set up the secure package system.  If you are unable to do so from the repository by explicitly specifying it, then download it from https://www.bchemnet.com/suldr/pool/debian/extra/su/suldr-keyring_2_all.deb and then

Code Select Expand


sudo dpkg -i suldr-keyring_2_all.deb


I have not worked with this particular printer, but I think the ppd explicitly depends on some of the Samsung binaries such as rastertospl.  So perhaps when you did this before, you also extracted those or had them installed from a previous attempt at setting up the driver.

It appears you do not have any of the packages from this repository installed, nor the driver using the Samsung installer.  You probably need to configure this repository and then install suld-driver2-1.00.39.

I am not sure why setting up the printer worked to select a driver that is not installed on your system, but that seems to be your situation.

Please post the output of the following two terminal commands:

Code Select Expand


apt list suld*

and

Code Select Expand


ls -l /usr/lib/cups/filter/raster*


Any idea what changed?

No.  Nothing in these packages has changed, unless you manually updated to a different driver version.  I suggest using

Code Select Expand


apt list --installed > ~/installedpackages.txt


on both your desktop and laptop, then using diff to identify what Ubuntu-provided packages may have been updated on one but not the other.

Is the issue fixed by reverting back to 1.00.29?  If not, my recommendation would be to completely uninstall all the packages and the printer, restart cups or reboot, and then re-install everything.

1.00.39 version doesn't work for me - it prints just completely black pages!

In the error log I can see:
D [13/Jul/2021:11:15:40 +0200] [Job 231] free(): invalid pointer
D [13/Jul/2021:11:15:40 +0200] [Job 231] PID 14518 (/usr/lib/cups/filter/rastertospl) crashed on signal 6.

The same issue is discussed here, but I didn't find a way how to fix it.
https://aur.archlinux.org/packages/samsung-unified-driver-common/

My interpretation of that thread is that solving the issue requires updating the driver, removing the existing printer installation, restarting (the system or just cupsd), and then adding the printer as a new printer.  So you might want to try that first (obviously you have done the first step).

So could you place 1.00.29 back into the repo, please? Thank you.

In the event you do not want to try the above sequence or it does not work, 1.00.29 should be available now if you refresh the repository listing.

Is driver2 version 1.00.29 deb package available for manual download anywhere?

I'm using it for my printer (SCX-3405W) now, so I'd like to have a chance to revert in case of any issues after upgrade to 1.00.39 version.

The deb for 1.00.29 is not currently available, but can be if there is a need.  So if you decide to upgrade to 1.00.39 and run into trouble, I can make it possible to revert back.

That said, there is no reason for you to do anything if 1.00.29 is working for you.  The fact that the 1.00.29 package is no longer available does not mean you must change to 1.00.39, or that there is any advantage to doing so.  I simplified the offerings because I did not perceive any dis-advantages - but for everyone with a working installation, leaving things as they are is perfectly fine.

Thank you for sharing.  I have made this sticky and linked to it from the web pages.

Note that the steps for modifying and overriding packages should not be necessary with the most recent update to the repository (eliminating most of the steps in the middle).  Also note that version 1.00.36 is no longer available and 1.00.39 should be used.

Minor update to a few packages to allow for installation on ARM systems (Raspberry Pi in particular) via emulation.

I have removed many packages that were of little or no use to anyone, based on multiple years of download data:
  * The "armel" packages that were never of much use (and whatever use they had is obseleted by the ability to emulate amd64 on ARM).
  * The Qt3 version of the Configurator and all associated old library files, which have been out of date for nearly a decade.
  * Driver versions 3.00.90, 4.00.35, and 4.00.36.  Use driver version 4.00.39 instead (or, if your printer is supported, 4.01.17 or driver2 1.00.39).
  * Driver2 versions 1.00.06, 1.00.27, 1.00.29, 1.00.35, and 1.00.36.  Use driver2 version 1.00.39 instead.
  * ppd-3 (was only required by driver2 1.00.06).

I have not created transitional packages of the eliminated versions, so users who have the old versions installed are free to continue using or to move to the later version.  However, it is no longer possible to install the versions listead above using the repository.  None of those versions are essential for any particular printer (as far as I know).  If for some reason you still need to do a fresh install of one of those versions, the installers from Samsung are still available for download.  You can also post to the forum and I will consider restoring a deleted package if there is a clear use case that requires it.

I did not remove driver version 3.00.37 because it still sees a surprisingly high use, but there really should not be any need for that version.  For a couple of printers, the limit is 3.00.65 (still available), and everyone else using 3.00.37 should really move to 4.00.39, 4.01.17, or driver2 1.00.39 if they support your printer.  I may eliminate it in a year or so.

See also the previous announcement about the limitations for the Qt4 version of the Configurator.  That version is not installable in any recent (mid-2020 or later) distro version, and insecure in any installation.  I expect I will remove those packages entirely in approximately 1 year.

This is done for the common & ppd packages.  (Based on my reading of Debian's package guidelines, adding the Multi-Arch line is not appropriate for the other "all" packages in this repository.  However, I do not think any of those packages are relevant for this purpose.)

Please let me know if it works for you without having to manually edit the packages.

You can find every Debian package ever released here:
https://snapshot.debian.org/

You would need to download the 2.2.12-2 packages for whichever cups* packages that you have installed, then dpkg -i *.deb.  Note that because 2.2.12 was never released for Debian 10 (it only briefly existed in unstable/testing), there may have been a dependency change that will cause problems.  If that occurs, you are probably better off downgrading to 2.2.10-3 using the same process, then pinning those packages so they do not update.

It appears that the Debian CUPS team backported a problematic change introduced in CUPS 2.2.11 to 2.2.10 (-4 and later).  You are running into the issue from this bug:
https://github.com/apple/cups/issues/5562

The bug is fixed in 2.2.12 and 2.3.x, but that particular fix was not backported by Debian to 2.2.10.  You can try opening a bug against the Debian package and see if the relevant committ can be backported.  Otherwise you will need to revert to an earlier snapshot of CUPS (2.2.10-3 or earlier) or manually update to 2.2.12.

The Linux driver cannot read printer messages.  It is indeed a Windows only feature.  I believe that all the printers can print out a status page, and that is the official alternative method, but obviously that does not work if the printer will not print.  It appears that HP is starting to release new printers based on the Samsung technology, but they have not made any meaningful updates to the driver.