Messages

You might want to try the 4.00.35-2 packages (use force version to select).

Sounds like a CUPS bug, if some printing methods work and others don't.  Not that I'm a fan of it, but Adobe Reader may help here for the same reason you can print via LibreOffice.

I don't know that it will help, but have you tried the pdf-fix package?

My guess (and it is a guess) is that the problem is something about the network configuration of the printer server, either a firewall issue or a network segment issue.  Have you tried the various troubleshooting steps for network scanning?

I've started the server, with no Errors, but when i've checked the log file saw the errors. Could you, please check the attached log file, to help me fix this.

No log file was attached.

Do you happen to know what the before/after the latest update kernel versions are, in case someone else has similar issues?

It is likely that it is not using the Samsung driver, but instead now one of the standard CUPS drivers that support the printer.  I'm glad it works.

Well, the problem might still be with the driver, but not the printer portion.  Without the scanner package, your scanner is using a different controller for the scanner instead of the Samsung one.  Regardless, I'm glad it works.

As to your aside: I know the password requirements are strict, but it cuts way down on the spambots.

Have you tried toggling the "PDF as standard print job format" option under Options -> Libreoffice -> Print?  It might help.

Recent changes to CUPS and the Libreoffice print system seem to be somewhat responsible for this sort of problem; I occasionally encounter a document that won't print correctly (or at all) from Libreoffice, but if I generate a PDF and print that it works just fine.  (It is also related to the Samsung driver, because I don't have the problem with an HP printer, but for me the issue developed following updates to components other than the driver.)  It has not occurred frequently enough that I have spent much time investigating.

Please share if you have continued problems, with whatever trends you notice.  When I have a chance, I'll try to look into this some more.  I'm hoping for a new Samsung driver update sometime soon, as they launch their new printers in April, which potentially could also solve the problem.

It's not a firewall problem at my end.  It may be that my web host has your IP range on some sort of block list; if your issue persists and you are certain it is not a configuration issue with your subnet, then I will contact them to see if I can learn anything.

Have you tried reading through http://www.bchemnet.com/suldr/scanning.html and following suggestions there?  There are also several other forum posts about difficulty finding scanners and the solutions.

If so, share what you have tried so that additional guidance may be possible.

Have you tried the instructions in this thread?  These is no reason to think it will be different with 12.10, except that 12.10 might work without any special effort.

I would assume a bug in the usb library based on this information.  Activating the sid respository and just updating the libusb system should be "safe" (I routinely pull packages from experimental and/or sid into testing when I need an update that is blocked by the freeze), and is the most likely single thing I can think of that might help.

Printer model: clx-3180
Linux dist: Linux Ubuntu 12.04 LTS
Connected: Network ipp
Unified Driver Configuration:
Version:
Common 3.00.71
Printer 3.00.24
Scanner 3.00.19
Build 279

This implies that you are using the 3.00.71 package from the Samsung installer rather than the repository packages.  I suggest starting by removing that and using the repository.  (Especially because although I know that is the "official" version for the clx-3180/3185, drivers between 3.00.65 and 4.00.xx were fairly spotty.)  However, the other issue could the use of IPP, which is not entirely reliable with some Samsung driver/printer combinations.  Perhaps setting up the printer with LPD instead would help.

Removing the packages removes everything associated with them.  However, if you ever tried the Samsung installer, it may have left behind files - follow the instructions on the website.  (That would also work if the packages are leaving behind files for some strange reason.)  Removing the packages does not itself uninstall printers that you have configured, because that is a user setting (otherwise an update to the packages would break all printers).

Have you tried the older driver version packages (e.g., 4.00.35 or 3.00.65)?  This series of printers seems to be the cause of at least half the recent posts about problems, so I suspect it may be quite finicky about which version of the driver is used.  That might also account for the "it worked before" issue.

Is this only an issue when printing PDF files?  My printer (CLP-550N) also works perfectly printing anything black & white, but routinely (not always) chokes on color prints unless I switch the driver to the CLP-500 (which is an SPL printer instead of PS).  Over several years I've never found a proper solution.  If you only have the problem with color PDF prints, then pursuing the issue as in this thread might make sense.  Otherwise (or in addition), you might want to try different drivers and/or print protocols to see if it helps.  (And possibly program printing from?)

Samsung has not released binaries that work on arm platforms, and since we don't have the source code......

But you might be able to use the trick here:
http://www.bchemnet.com/suldr/scanning.html#3

The #### code for the SCX-3200 is 3441.

Older versions are still available, so you should be able to revert back to what you had working by manually selecting the older package versions.

Your solution implies that you actually don't need the Samsung driver at all - the one you have selected is the foomatic one available through the normal repositories.

I'm not sure what to make of this.  I can find scattered reports of similar behavior from libusb-1.0-0, but nothing that is particularly useful for troubleshooting this (and it's not even clear whether the syslog messages are meaningful).  Perhaps try installing the version of libusb-1.0-0 from sid?  It is a more recent release and might solve the issue.  You might also try installing usbview to see if it reports anything odd, but I wouldn't be too optimistic about that.

There's also the possibility that simply moving which USB port it is plugged into will help.  Although that shouldn't matter, it occasionally does.

What have you already tried, of the various suggestions on the web page and the forums?

I suspect mfp just searches through the devices, open it for writing, and then writes.  The difference is that it knows what the timeouts should be, and if the printer prefers any additional information, etc.

I'd like to hear from Samsung about what ALL the driver pieces do, or just have them open up the source.

Thanks for sharing, I will include that as a possible solution that next time I update such information.

Local availability is pretty variable, but I have not had any issues with internet orders of any toner.  And I don't know that my use is typical, but my Samsung cartridges certainly last a long time and don't degrade noticeably even after 3-4 years of use.

I also have to comment that as annoying as my Samsung printer is at times, it really does significantly out-perform the "comparable" HP printers that I also regularly use, at least in terms of print quality (the HP printers are quieter and substantially faster).  So it is definitely worth looking carefully at specifications and reviews before making a final decision.  (My printer hasn't been sold for years, so that's not directly appicable for you.)

If it is an authorization problem, perhaps printing as root would work, or making sure your user is added to the appropriate group?

In my experience, HP printers are by far the best supported under Linux, and I have never encountered one (admittedly not a huge sample size) that did not install easily and with a full feature set (often more features than under Windows) using packages available with any current Linux distribution.

Most Samsung printers and setups also seem to work well, especially using this repository - something close to 10,000 people (from all over the world) seem to be using it now, and relatively few do anything other than install a basic of set of packages and go.  So while problems certainly exist, most people don't encounter anything other than the need to set up this repository to access the drivers.

Based on my research when I was recently in the market for a new printer, Brother, Oki, etc. are all comparable to Samsung in Linux support - usually it works, but not necessarily using standard drivers available in the distribution and there are some difficult cases.  However, I'm not aware of an equivalent support group/external repository to deal with any other manufacturer (which isn't to say they don't exist - I haven't looked very hard).  A few companies are still truly awful with Linux support, and it is much harder to determine in advance if a printer will work.

So all things being equal, I would probably recommend HP.  However, not all things are equal.  So if a Samsung printer that meets your requirements is cheaper, or higher quality at a particular price, or simply gets much better reviews than a comparable HP, I would certainly not discourage you from purchasing the Samsung.

None of the errors seem to be critical.  Have you tried to actually configure the printer with CUPS at this point?

This brings me to the next question: Is there a way to send a fax with the printer drivers? Because the Android app can send faxes, and I believe so can the Windows and Mac OS software...

Not that I am aware of.  But when I have a chance, I will see if I can learn anything useful by looking at the Andriod app.

I will package this up and add it to the repository, sometime in the near future.

For Ubuntu 8.04, you may need to use the samsungmfp-driver-legacy package; I don't know if the libc6 with that release is current enough to work with the later driver versions.  As long as you don't try to install the configurator packages, there should be no need for X or QT packages.