Messages

Thank you for sharing.  I have added this as a solution for scanning problems.

You appear to have set up both the "stable" (currently Stretch) and "Jessie" repositories.  There may be some conflict there with the vlc libraries as a result.  Try disabling the "stable" repository, refreshing your lists, and installing the configurator package again.

Alternatively, installing the qt3 version should probably work, because the dependencies will mostly draw from the suldr repository rather than debian.

Thanks for sharing.  I am going to decline to incorporate it into the package at least for now, because this adds an unnecessary step for those who don't want to mess with the source.  If it could be modified to default to something reasonable in the absence of setting the specific source, as it does now, I will include it.  I suspect I know how it could be done, but I don't have a test system to check it with.

You should contact Samsung support directly for issues using printers with Windows.

Unfortunately I cannot offer any additional advice beyond what is posted on these forums and the website.  I don't have any personal experience relevant to this situation, and have never used Simple Scan.

The driver only operates the printer.  It has nothing to do with setting up the printer initially.  That process is handled by whatever system handles all printer installations.  If the printer is automatically detected by your system and configured, it may (or may not) select the correct driver, and/or may prompt you for the correct driver.  If the printer is not automatically detected, you will have to manually trigger the new printer installation through whatever tool is appropriate on your system.  To use the Samsung-provided driver, make sure you are selecting a driver called "Samsung Series...."; other drivers with "Samsung" in the name are usually an open-source alternative.

To tell which driver you are using for printing, you probably have a "Printing" or similar option on a Systems Tool menu.  (If not, you can access it by typing "system-config-printer" in a terminal.  In the event that is not installed, you can install the package the normal way.)  Then select the printer, go to Printer menu -> Properties, and look at "Make and Model".  If it starts with "Samsung Series..." it is the Samsung driver.  You can change the model here as well.

As far as the scanning, you will just need to keep trying different drivers until you find one that seems to work for both.  That is why there are so many drivers available in this repository.

You can try any version starting with 3.00.65, including the driver2 options.  The 4.00.36 is just the last time an update seems to have directly targeted this printer.  Based on what you are describing, I suspect the latest driver2 is probably your best bet.

If you run

Code Select Expand


sudo gedit /etc/apt/sources.list

and delete any exact duplicate lines containing "bchemnet" in them, the warning will go away.  But it doesn't hurt anything if it appears.

I believe xsane saves files into the home folder by default.  You should be able to check and change it from the Preferences menu:
http://www.xsane.org/doc/sane-xsane-save-doc.html (under "select filename").

You can try 2 things.  The easier one is to try to have Libreoffice change the way it outputs print jobs.  Open Libreoffice to a new file (any type), then go to the Tools Menu, Options, and select Print under "Libreoffice".  Uncheck (or check) the box next to "PDF as standard print job".  Click OK and try to print again.  If it still doesn't work, it is probably best to leave that option turned on (checked), so adjust it if necessary and try the next option.

The more involved option is to install the Samsung driver and use that.  You can set up the repository as described on the main page, through the SULDR link above.  Once you have the repository set up, choose driver2-1.00.36 to install.  You will then need to add your printer again as a new printer.  During the process, you may have to choose the correct driver (Samsung....M283x) or it may automatically pick it up.  The default Ubuntu driver might be the default, though, even with the new driver installed, so you should check to make sure you are using the M283x driver.

Download the Samsung installer v1.00.36 from the Samsung Installer page on this site.  Then extract all files, in Nautilus.  Assuming that you did all this on your desktop, you should now have a "uld" folder on the desktop.

Open a terminal.  Type:

Code Select Expand


cd Desktop/uld
sudo ./uninstall.sh

And it should remove all the installed pieces.  You can then delete the downloaded file and uld folder.  You can now install whatever versions you would like to try through Synpatic.

The reason that you do not see it in Synaptic is that the installer adds files without telling the rest of the system what it has done.  "Packages" as .deb files (like I provide through the repository) include information that Synaptic and related programs can use to keep track of what was installed, for easy removal/update.  Much commercial software does not do this.

"Permission denied" probably means that the Samsung installer never really installed anything.  You can check by uninstalling the packages from this repository through Synaptic (which should work fine), then in a terminal type (without quotes) "ls /opt/".  If you see a listing like "smfp-common" or "Samsung" then you should follow the uninstallation procedure for version 1.00.xx on the Samsung Installer web page here.  If not, you are clean.  Then re-install through Synaptic, whichever version you want to try.  If one version doesn't work, you can try another, and the packages will automatically install/uninstall as needed.

If you downloaded files from Samsung's website to install, they will be the last (Version 1.00.xx) because that is all that Samsung presently provides.  If you only used Synpatic to install components, then those instructions don't apply to you.  You can safely leave any package installed through Synaptic in place.

No.  But if you run the Samsung uninstaller, it should clean up okay.  With recent versions, even if it misses a couple of things you should be okay to install the packages from this site.

Type "cd Desktop" (without quotes) in the terminal, prior to issuing dpkg command.  When you open the terminal you are in your home directory, not the Desktop.

It is not normal but not harmful.  Chances are that you do actually have duplicate entries in /etc/apt/sources.list - this happens to me every year or two on one or more of my systems with one or more repositories, but I have never investigated what causes it.  Deleting the duplicate lines (edit the file as root/sudo) and then reloading repositories (apt-get update or equivalent) takes care of the warning.

The error is of no concern.  The message is correct - the email address field does not follow Debian (Ubuntu) package policy.  But that is completely irrelevant to your ability to use (or trust) the package.  Lintian is the Debian tool to ensure that all packages conform to a very strict set of rules, and the vast majority of its warnings and errors are about trivial items.  A great many packages in the Ubuntu repository fail one or more lintian tests.

I have no idea why someone decided that this particular issue was so severe it needed to be brough to the attention of the standard user, who has no reason to know what it really means.

Of course, full disclosure forces me to point out that I made the package, so it would not be unreasonable to ignore my advice on this issue.  Theoretically I could have a nasty plan in mind, and I am unwilling to invest the time to meet the package standards to prove otherwise.  However, ~3500 people install the package every month, and I think that's about all you are likely to get as a second opinion.

It sounds like the driver is just ignoring the dpi setting.  Some do that.  I don't know why.

If it is possible to change the default on the printer itself, that might have an effect.

Do you mean
1. that you can only select 600x600 (1200x1200 is unavailable), or
2. that if you do select 1200x1200 then it does not print?

If 1, then you might be able to just change the default dpi in the ppd file to be 1200 instead of 600.  Both resolutions are listed there.

If 2, it may just be a problem with the driver that cannot easily be fixed.  I have experienced cases where a printer would not actually print at the highest available resolution with the linux driver.

I suspect some sort bug in this release of Mint.  This printer has been reported to work several times, so a change in the distribution rather than a problem in the driver seems likely.  If you have tried all the scanning troubleshooting suggestions that seem to apply to your situation, I recommend filing a bug report with Mint.

You can try using a different USB port.

There used to be an issue with certain scanning software where the scanner would be sent a "sleep" signal after a scan, so then it had to be restarted or unplugged/plugged in again to work for the second scan.  I'm not aware of any Samsung scanners that were affected and it was supposedly fixed years ago, but you could try a different program to do your scans and see if that makes a difference.

Otherwise, not really.  It may be an issue with the USB software rather than the Samsung driver, but historically bugs that have been filed citing issues with closed-source software like this driver have been closed without resolution.

Thanks.  Fixed.

I suggest trying suld-driver2-1.00.36.

1. The last report I have of a working install is Ubuntu 14.04.  I have no idea if that means it isn't working later or not.  As far as models, whatever has been posted to this forum is what I know.
2. Scan to PC is independent of the driver, and should theoretically work with any version.  However, the driver-4.xx versions are probably the only ones that received significant testing.
3. As of the last time packages were updated (3 years ago), there was no need to install additional dependencies.
4. I don't know.  The developers have not contributed anything in 3 years, likely because they are no longer using it themselves.  I have never had a system with which to test this.  The project is effectively abandoned unless someone wants this functionality badly enough to work on the code and update it.  It is possible that a change associated with changing to systemd are why the service no longer works as expected, and it might be an easy fix for someone with time and enough knowledge.

Try installing the Ubuntu package libusb-0.1-4 if it is not already installed.

I don't think there is anything that can be done with the driver.  You could try forcing a refresh of the USB ports upon waking from suspend by modifying the suspend parameters.  I have not had to look into how to do this under systemd, but there is presumably a parameter that can be passed to do this.

Thanks for sharing.  Now that libusb-0.1 is no longer standard in the newest distributions, I will make a note that it needs to be explicitly installed for the driver to work.

I don't think the driver was ever intended to be deployed in this sort of setting, so I don't think there is anything about the driver itself that can be changed to address this.  Perhaps there is some way to modify the network configuration or use some sort of port forwarding to work around this limitation, but I don't have any experience that I can share.

I suspect many others have a similar problem.  I get many thousands of hits every month on the server for incorrect repository configurations, and now that you have explained this I suspect that a large portion, maybe most, are due to being set up as a PPA.  I will add this as a note to the setup instructions.

The repository is not a PPA.  I'm not sure if under Ubuntu-based systems if there is a separate process for adding PPAs vs other repositories; I know in the past Ubuntu has added an extra interface that is not actually part of Synaptic and that can sometimes modify the information entered for a repository in unexpected ways.  I suggest just adding the deb line directly to /etc/apt/sources.list, which should avoid anything happening when adding through the graphical interface.