Messages

This is fixed.  The repository is now signed by the old and new key with appropriate hash.  The old key will be dropped in a few months once the new key is installed on users' systems via the new keyring package.

If you are configuring the printer manually and selecting the M2020 series driver, you only have 1 driver installed if you only see one option for that printer.

You can be even more certain by uninstalling all SULDR components and then trying to set up the printer again, and seeing if it finds an appropriate driver.

It appears that the 2026 is identical to the 2020, and the same as the 2022 except with a slower processor and less RAM.  So I continue to assume the 2020 driver is correct.

That leads me to think that one of the following is true:
1. The printer RAM is too low.  I've seen this with other Samsung models from Linux, where a small amount of printer RAM made it impossible to print anything other than very simple documents.
2. Despite all appearances, the printer isn't really the same as the 2020, and there isn't a driver for it in Linux.
3. Something is wrong with your printer.  The way to test this would be try to print from a Windows or Mac machine using those drivers.  A virtual machine would probably work if you have one handy.
4. There is some minor issue in the way the driver is packaged, and you should install the driver using the direct Samsung installer instead of the packages.

If you can't do #3 and/or it doesn't help, and #4 doesn't help, then you probably will have to contact Samsung or consider an alternate printer.

Which driver are you choosing?  I'm assuming that this printer is part of the M2020 series, which 4.01.17 doesn't support.

It sounds to me like a potential bug in xerox_mfp, which is part of the SANE project.  You might try a bug report directed to them.

The lack of ADF in smfp is presumably Samsung simply not implementing that within their own driver, which is unfortunate but unlikely to change.

Have you tried a newer driver, such as driver2-1.00.36?

I will look into this.  It probably won't be for a couple of weeks.

Thanks for sharing.  I will update the information for this printer.

Creating a proper package to maintain the key has been on my to-do list for a while, and will address this problem.

I will move it up in priority and get to it soon (maybe a week, maybe a month).

You do not need to manually launch the driver.  It will be invoked as needed after the printer is set up.

Samsung's license has no restrictions on use of the driver as long as the driver itself is not modified.

You should not need to add/remove any translation files in /var/lib/apt/lists/.  The necessary ones should be picked up automatically and the rest ignored.  You could try removing the three for suldr and seeing if they are automatically replaced to solve the connection problem.

I can't help with the smart panel.  I have never spent any time working with it because I never had a printer that supported it.  If you are installing one of the most recent (driver2) packages, it is reasonably safe to use the Samsung installer directly, especially if it improves features.

I think it is a configuration problem on your server, but I don't know why.  Another possibility is a bad cache of a route to bchemnet.com, which a server restart, network restart, and/or router restart may solve.

Nothing has changed about the server at my end, and I don't have any trouble connecting with apt.  It might relate to is the internationalization files, if the locale that you are using doesn't match something on the server.  What locale do you have set?

Have you tried resetting your network connection and/or restarting apt-cacher to see if forcing a fresh connection works?

I have been told the block is removed, so you should have access again.

I have not configured anything that would block this IP.  I have opened a ticket with my hosting company to see if they can resolve it.

You should contact Samsung and let them know this.  There seems to be enough interest for them to release an armhf driver, but I don't know if people are actually telling them.

In the meantime, I am not aware of any solution for that particular printer.  It does not seem to be supported by any of the alternate drivers.  You might have some luck trying to use it as a "generic" printer, but without any printer-specific features.  The only other option I can think of is to create an amd64 or i386 guest as a virtual machine installation (I think Xen can handle this with an armhf host?), install the driver in the guest, and run the printer that way.  But I can't be sure it will work at all, and it may be a considerable amount of effort.

This would have to be reported to Samsung, because I only have the binary files.

But if 1.00.29 works, there probably is no reason to move to a new version.  New versions often break things that work with prior versions, which is why I provide so many different ones as packages.

The answer is that yes, it is supported, but only if you configure the system correctly from the very beginning.

The issue has to do with "soft float" (armel) vs. "hard float" (armhf).  The difference is whether floating-point calculations are done by the processor (hard float) or software (soft float).  The original ARM processors, including the one that the first Raspberry Pi was built on, did not have a hardware floating point processor, and so were all "armel".  This is what Samsung released a driver for.  All current Raspberry Pi devices (I believe) can in fact run as armhf, and that is the version that is provided if you download an installation image from the Raspberry Pi foundation.  You cannot use the Samsung driver this version, and based on the "armhf" in your output, that is the version you are using.

It should (I think, not tested by me) be possible to download and install an older armel Raspbian installation from Raspbian.org, and that will work with the printer driver - at least for the versions that Samsung released an ARM-compiled version.  The downside to using armel when armhf works is that some processes will be slower and more energy-intensive, because software calculations are not as efficient as hardware ones.

So if you want to use the Samsung driver, you would need to download and install a fresh image of Raspbian that is armel instead of armhf.  There may also be a loss of access to some packages in other respositories as a consequence, I don't know how many other things are currently offered as both armel and armhf.

If the latest driver version (driver2-1.00.36) does not help, then those features probably just don't work.  Samsung rarely updates the driver to solve problems like this.

Sorry, no.  I suggest reporting the issue to Samsung.

Sorry, Ubuntu reference is obviously inappropriate, force of habit from the source of most questions.  Under Debian, you should have a Printing utility installed.  If not, install system-config-printer to get it.  Then manage the printer that way.

Try adding the printer using the default Ubuntu printer tool instead of the Configurator.  You do have the Samsung driver selected (the "series" in the name is usually the clue), but the Configurator is installing it as an mfp device which doesn't always work with new distributions.  The default tool should automatically detect it on a different connection, but may default to a different driver unless you manually select the Samsung one.

How are you setting up the printer?  Are you relying on automatic detection or manually selecting the driver?  In either case, do you know which driver is being selected?  There are two non-Samsung drivers (splix & fooqpdl) that partially support this printer, so it is possible one of these is being used and causing the issue.

The Samsung installer for driver version 1.00.37 (December) is available on the Samsung Installer page, but I do not plan to package it.  The only differences from 1.00.36 are the ppd files for the M301x, M306x, C3010, and C3060 series printers, none of which appear to be actually for sale yet.  The driver itself is identical to 1.00.36 (and therefore also 1.00.35).

Driver version 1.00.36 is now available.  The only significant changes are updates to many ppd files and a couple of minor fixes to the packages, together which should probably address many of the problems some people have had with the 1.00.35 driver.

I mean that in the list with drivers shown I scroll down (a lot) and I have a driver named exactly SCX-4216F. This is in Ubuntu Mate 15.10. For me SCX-4x16 does not work - printer starts to print and then it does not finish, not even get the paper from the tray.

That driver is provided by splix, and is not part of the Samsung packages.  So to see it, you would also need to install printer-driver-splix.

The drivers are both 32 and 64 bit.  The packages that it reports as failing don't exist, though - the "common" and "ppd" packages do not have architecture-specific binary files, and so it should be trying to pull those as architecture "all".

I think there is a problem with the way your system is handling multiarch.  However, Ubuntu doesn't seem to configure it the same way as the base Debian system, so I can't offer you an immediate suggestion.  I am sure that it has to do the way dpkg and apt are configured, and if you look for resources about installing multiarch packages under 64 bit for Ubuntu you can probably find a solution.  The errors you are getting are not specific to these packages.

Ubuntu seems to have removed that option from apt-get.  I have no idea why.

Try sudo apt-get install suld-driver-4.01.17:i386

If that also doesn't work, then perhaps Ubuntu has added some alternate way to force 32-bit installations.  But you would have to look at Ubuntu resources for that, I have not kept up with their changes to the underlying Debian system.

You might be best off installing the x32 version in the x64 system if that seems to be working.  Using the repository, you can do this by entering the following in a terminal:
sudo dpkg --add-architecture i386
apt-get -a=i386 install suld-driver-4.01.17

Replace "suld-driver-4.01.17" with whatever version of the driver you actually want if you prefer a different one.  It is likely, but not definite, that installing the x32 version of the smartpanel from Samsung will also result in a working program after this.

The files are additional binaries required for specific printers, that are called as needed by the universal Samsung driver.  For the most part I don't know what they do, but the errors are not themselves a problem: they are in fact not normal driver files, so it does not surprise me that CUPS complains about them, and the errors do not indicate anything is wrong with them.

Unfortunately I have no alternate ideas of what might be wrong based on your description.