Messages

Two things you can possibly try.  First, just make sure it isn't an issue with Xen, do you have a machine running Linux natively that you can connect the printer to?

Second, I am very close to releasing updated packages that might help with this issue if isn't due to Xen.  My goal was today, but that isn't going to happen - more likely another 3-4 days.

No.  The Samsung Unified Linux Driver is only available for i386 and amd64 architectures.  Because the driver is not open source, I have no control over this limitation, nor will you be able to locate any source code.

Your sources.list should exactly like this:

deb http://www.bchemnet.com/suldr/ debian extra

From the example you give, it likes like you may have a typo (sludr instead of suldr) and/or be missing part of the line.

I'm not sure what else to try, unless you happen to have another computer available to try with the printer to test for a different result in the event it is a subtle hardware issue.  This printer is normally well-supported by both the Samsung driver and SANE natively, but I do occasionally hear from other people who simply can't get a particular printer/computer combination to work.

Try this:
http://bchemnet.com/suldr/questions.html#17

Okay, try explicitly adding everything:
apt-get install samsungmfp-driver-4.00.35=4.00.35-2 samsungmfp-scanner=4.00.35-2 samsungmfp-configurator-qt3=4.00.35-2.2 samsungmfp-common=4.00.35-2 samsungmfp-configurator-data=4.00.35-2 samsungmfp-network=4.00.35-2

Sometimes apt is configured to be too insistent on the latest versions.

Try adding the explicit samsungmfp-common version:
apt-get install samsungmfp-driver-4.00.35=4.00.35-2 samsungmfp-scanner=4.00.35-2 samsungmfp-configurator-qt3=4.00.35-2.2 samsungmfp-common=4.00.35-2

You need to allow all incoming UDP packets on all ports (or at least > 1024) from the printer.  The netdiscovery tool uses UDP on a variable port.  The iptables rule is something like this:
iptables -A INPUT -p udp -s PRINTER -j ACCEPT

Where PRINTER is the network name or IP address of the printer.  (If the printer is on a static IP, that is more reliable because network names do not always resolve when the firewall first loads upon boot.  If it isn't static and the name isn't resolving correctly,  you can use a range of IP addresses, such as 192.168.1.0/24, to ensure that whatever dynamic IP address it has is in the allowed range.)

I have never used UFW or GUFW, and from the available documentation it is not obvious to me how one could set up this rule using that interface.  Because GUFW is 2 steps removed from the actual firewall (iptables -> ufw -> gufw), you may give up a lot of flexibility using it.

I don't use it, so can't say for certain.  But I suspect that the answer is "no" unless you either uninstall it or disable whatever script is starting it upon boot (but that may also render it useless).

apt-get install samsungmfp-driver-4.00.35=4.00.35-2 samsungmfp-scanner=4.00.35-2 samsungmfp-configurator-qt3=4.00.35-2.2

The ".2" for the version of the configurator was left out of my previous post.

Use this to get the older packages (you will probably need to remove all existing samsungmfp packages first to ensure dependencies work correctly):
apt-get install samsungmfp-driver-4.00.35=4.00.35-2 samsungmfp-scanner=4.00.35-2 samsungmfp-configurator-qt3=4.00.35-2

It looks to me like your hardware is being mis-identified.  Have you tried using different USB ports?

You might also want to try the 4.00.35-2 package versions, which have the older scanner binaries and might work if there is just some odd interaction on your system.

Hi there. First thanks for your useful help. I followed all your instructions and Ubuntu 12.04 recognizes the Samsung scanner. But, when I re started my computer and I logged into Ubuntu a Samsung window appeared (I attached it). After that I tested my new scanner using Xsane scanner program. It works great, but I found the following problem:

The popup is the smart panel, which I don't deal with, and not the driver itself.

All the images that I scanned had a section of the letter size. (I attached one).  I checked the Xsane scanner program, I found the following information: 12.80 cm x 14.70 cm. I couldn't modify this option on the Xsane scanner program configuration.

Do you have the preview window open (window -> show preview)?  That provides the interface generally used to change the size in xsane (whether or not you actually use the preview).

I decided to use the Samsung Smart panel, but it didn't work.

Any idea, how to fix this problem?

Thanks in advance.

The smart panel (I believe) is just for interfacing to specific printing features.  You need the Configurator to control the scanner.

That is what I meant.  When I have some time (probably not for a month or so), I'll see if I can come up with anything else.

Try these suggestions if you haven't already:
http://bchemnet.com/suldr/scanning.html#1

Post again if none of those helps.

Try this:
http://bchemnet.com/suldr/scanning.html#3

Otherwise installing the samsungmfp-scanner package from this repository will pull in the necessary bits.  You can still use the existing printer driver without any changes, whether you use the print driver from this repository or not does not affect the ability to use the scanning part (though the printer driver will have to install).

The only immediate possibility that comes to my mind is a group issue (e.g., not being in the lp group).  I agree it's a bit odd.

When I finally get to this, I'll include all the changes you've made into the repository.

You're welcome.  I went through a similar cycle of frustration with the driver and a Samsung printer several years ago.

http://www.bchemnet.com/suldr/questions.html#3

If you want the PSU and smartpanel, you can get them directly from Samsung; the versioning of those is essentially independent of the driver, so the downloads provided for your printer should work.  (And if they aren't provided for your printer from Samsung's website, they probably wouldn't work anyway.)

What packages are you referring to in Mint repository ?

http://www.bchemnet.com/suldr/
That repository will work with Mint as-is.

This sounds like either a complex interaction between glibc, cups, and the driver that only appears with the particular combination of versions you have on your Fedora 17 system, or it is just another quirk of the Samsung installer that it simply does not work well on all systems.  For your Mint systems, I suggest trying the repository - many people have reported that installing with the packages is far more reliable, possibly because the dependency resolution is much better than the script used by the Samsung installer.  For your Fedora system, either update to Fedora 18 or use alien to convert the .deb packages you want to .rpm.

In a few months I may have time to look into building proper .rpm packages for Fedora users, but that's a large time investment I simply can't make right now.

What conflict are you getting, and are you using the Ubuntu package or the download from Google?  Although I don't use Google Earth, I just downloaded the 64-bit .deb from Google and it had no conflict on my system when preparing to install.

I'm not sure what to make of that, particularly for Mint.  There have been conflicts between particular libc versions and the driver before, but 2.15 is standard in Ubuntu 12.10 which numerous people have reported working (I'm still using 2.13).

Are you using the Samsung installer or the packages?  And if the latter, have you tried different versions of the driver?  If you are using the Samsung installer, trying the installer for a different printer may work around the issue (there are various versions on this website).

I wanted to ask furthermore if there is a way for me to have the scanning source of this maschine autoselected in libreoffice writer. Since everytime i log in to my ubuntu (64bit 12.10) i have to select source of importing scanning software.

I'm not aware of any way to do so and can see no indication that there is a setting to store that information in.  I don't generally use that interface, but a quick test on my system (Libreoffice 4.0.0 on this particular machine) indicates that the insert -> picture -> scan -> request only works after I have first selected the source.  Which is slightly odd, because "select source" works with the scanner regardless of the source actually selected.  (In my case, the interference is a USB camera and the scanner is a Canon flatbed, so this is an issue that has nothing to do with the multifunction aspect of a printer.)

Filing a wish request in their bug tracker might be the way to go.

You can try removing that printer and configuring a new one to get an appropriate driver match.

Failing that, uninstall the driver you downloaded and try again using the repository packages provided through this site; many people who have trouble with the "official" drivers find they work fine via a package setup (even though the binary files are identical).

I'll look into this when I have some time.

Interesting.  15-20% of users of these packages install the -lpr one, but you are the first to point out a bug that must have existed since I packaged 4.00.39 a few months ago.

Anyway, I think the problem has to do with the recent bizarre renaming Samsung did to add the ".app" to everything, and the link in /usr/local/bin should point to /opt/Samsung/mfp/bin/slpr.app instead of without the ".app" (not in addition).  I've never really used this utility, so didn't catch this when packaging the new versions.

I believe that the link replacement will also address the lack of output you observed, because "lpr.app" is not something that would normally be invoked during a print cycle.

@bchemnet: Have you already packaged this and added it to the repository? What would be the package name?

Not yet, my to-do-immediately list hasn't cleared enough for to spend time on it yet.  But you can still use the attachment in this thread.

There are quite a few Launchpad bug reports for 1.6.1 that have something in common with what you describe, which suggests that something broke in CUPS.  The only possibly relevant information I can see is this:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1053443/comments/35

If that does not help, I suggest opening a bug report on Launchpad; nothing about the Samsung driver should be causing the behavior you describe, and CUPS has recently updated whereas the driver has not.  I'm still running 1.5.3, so I don't know if the issue affects many Samsung printers or not.