Messages

I suggest trying one of the driver2 versions to see if you have any better success.  Otherwise, there have been various reports of issues with newer SANE versions.  Perhaps a distribution update or filing a bug report there will generate something useful.

Have there been any developments on this front?

None that I am aware of.

This sounds more like an issue with SANE than with the driver.  Perhaps filing a bug report with that project (or through your distribution) will generate a useful response.

This printer should, in theory, work with 4.01.17 and also the driver2 versions.  You may want to try some of those if you haven't already.

My only suggestion is to try one of the driver2 versions, if you haven't already done so.

I have uploaded packages for two new versions of the driver, 1.00.27 and 1.00.29.  I have also updated updates to 1.00.06 and 1.00.21 that may address some issues.  No testing has been performed.

You are correct, thanks.  I will package this as soon as I have time, but that is unlikely to be soon.

Which package did you download from Samsung?  Directly or from this website?  If you downloaded directly, was it from the Samsung site associated with your country?

This appears to be a bug with a few printers with the latest version of the driver.  Samsung eliminated that driver file but did not remove all references to in some of the printer instructions.  Your best option is to try one of the older drivers.

As far as I can tell, nobody is providing a sane-backends or equivalent package for that type of device.  You might be able to compile it from source, but I have no personal experience that would be helpful to you.

You can try posting in the development thread to see if the original developers of the scripts can help.  I can see where the problem is, but don't have a device with which I could test any fix (and honestly don't have time to debug it even if I did).

SANE is probably available as a package (such as "libsane") through your package manager, if by "device" you mean some sort of computer.

If you mean something like an Android device, I'm not sure whether or not SANE works.

This sounds like it could be a bug in CUPS rather than the Samsung driver.  The only way I can think to test that is to have another printer (different brand or model) and try that.

Or perhaps there is some odd communication error with your particular printer.  This model has been reported to work multiple times in the past.

Sorry I can't provide a specific solution.

Samsung presumably could create an SPL driver if they felt the need.  Since they didn't, I'm assuming they won't - some of their printers simply use PS.

It may be possible to modify the PPD as you describe to utilize the SPL driver, but I have no experience with that.  I have modified PPDs in the past, but never to the degree you are describing, and even then only with mixed success.

This is not to discourage you, but just to point out that there isn't an easy solution.

It looks like a typo.  You have "extras" where it should be "extra" (no "s").

I still do not have the 'scan from the printer keys' working.  I'll keep working on that and update.  Also I've not noticed a noob level set of instructions on how to setup the repository.

The suld-scantopc packages (scanner server) were written for this purpose.  They are still a work in progress, but if you don't have immediate success you can post to the corresponding forum board for assistance.  (I just provide those packages, I don't maintain the actual scripts involved.)

I'm willing to write a how to from the perspective of someone who's never worked with APT, describing my journey.  Any comments as to where I should put such a post?

If you are interested in doing so, the "Using the Repository" board would be appropriate and most likely to be seen by anyone looking for such information.  And maybe one of the Ubuntu Forums or some other forum, but I don't keep track of any of those any more so can't say for certain.

The netdiscovery component is installed with the suld-network-2 package, which should have been pulled in when you installed the driver.  If not, you should manually install it.  If it is missing, adding it may solve your problem with no further work.

On the other hand, if it is present, I'm not sure what to say other than there have been several recent reports of inability to detect network scanners following system updates.  Obviously something has recently changed in a non-MFP package that is breaking the MFP detection behavior.  However, nobody has successfully identified what it is or reported that they have filed a bug with their distro that might address the matter.  I do not have the means to test this particular behavior.

I suspect that something, perhaps the SANE version, that changed from 13.10 to 14.04 is the actual problem.  However, the latest drivers ("driver2") use a different set of Samsung libraries, and perhaps that will resolve the problem.

If not, I suggest filing a bug with Ubuntu or the SANE project, because a change there appears to be at fault.  Otherwise, I'm sorry but I do not have any other ideas.

Only armel files are provided by Samsung at this point.  I know that most Linux systems are actually using armhf, so your best approach is to contact Samsung and ask them to provide armhf drivers as well.  Your only other choice is to switch to armel (which armhf hardware supports), but all I know about the process is that it is possible - I do not own any arm-based devices.

There probably isn't a solution to this.  The Configurator has not been updated significantly in several years, and with Samsung's decision to discontinue it entirely a year ago I suspect any limitations just have to be accepted.

Have you tried a different program - such as xsane if you are using the Configurator, or vice versa?

I'm assuming that you don't have any setting that says "print grayscale" or the equivalent selected anywhere.

You could try a different driver that doesn't match the printer model - sometimes this works.  Perhaps one of the other CLX-6xxx models?

This sounds like something that should perhaps be filed as a bug with the SANE project, or at least posted in a forum more focused on that project in particular.  What you are describing sounds like a bug in one of the libraries - possibly only for Samsung devices, but still a bug in that project.

I have posted packages for the 1.00.21 driver (driver2-1.00.21), which Samsung released in March.  I have performed zero testing on these packages.

I've moved the topic so that you might get better visibility to people who can help you.

I am about to post slightly modified versions of these packages, which may address your problem.

I have no experience sharing with a Windows computer, so I don't know what the solution might be.  You could try the latest driver (1.00.21), which I am about to post - but it may not be a Samsung driver issue.

I am about to post a new driver version, you could try that (driver2-1.00.21).

As a temporary fix, I will add both names as resolving this dependency to the latest release of this package.  Hopefully it won't cause additional problems for those using the newer library.

Thanks for sharing the solution.  I will add this as a possible solution for network issues.