Hi deano_ferrari
Thanks for your answer.
You are right about the text file. I tried to paste all the text from the error log twice and both times the answer to create was “Page not found”. The size of the error log is by now 878kB thinking that might be too much I just sent you the name of the file. I have now pasted only that part of the log file from today. That was possible:
http://paste.opensuse.org/16005623
May I remind you that both printers worked fine before those last opensuse updates.
For the ML2010R I have three Samsung drivers (also the uld version), which all seem to be different and the OpenScripting Foomatic driver, which I used since the beginning with opensuse 13.1. The Samsung unified driver for the printer can be started from the root desktop. If I tell the Samsung program to test the printer, the result is ok, only the printed page says there is an internal error and no test page. I have always used Yast to install printers, but today I encountered html cups via localhost and tried that way to create a new printer. The result was the same as with Yast. I pasted three screen shots of the tests:
http://paste.opensuse.org/86873013 http://paste.opensuse.org/39625857 http://paste.opensuse.org/3134233.
Only with the Foomatic driver there are now a few pdf files being printed, don’t ask me the difference, that did not happen yesterday. Yesterday I used always the same pdf file and then discovered, that print preview displayed an empty page. Now I use a pdf file that displays a real output as print preview. No documents of office or text files or anything else are being printed.
The forum thread you mentioned is mostly about the Samsung Unified Driver, that I use on this and the former suse variations.
Maybe the drivers I have are quite old, but the ML-2165 was bought in spring 2014, so the driver should be not too old. I downloaded the driver after the purchase. There are no longer special drivers for the ML-2010R on Samsung support, but I have all the old CD’s (including a copy) and of course those versions on the laptop.
Today I have read a lot about problems with cups and that it may be advisable not to update if you have a working configuration. So maybe it would be wise not to update automatically such a sensitive system as happened here. I am no printer specialist and all those different versions of cups-filters and ghostscript-filters tell me nothing. I have also found the statement of one suse specialist in the bugzilla, that cups is not being changed on the commercial versions - what seems very wise.
I tried in the last days also the way back to cups 1.5.4, but that was no success. No printer detected and no print output. That was how it all started, suddenly without having changed anything personally there was no print output.
I have no idea since when cups 1.5.4 and its surroundings was used, but it must have been quite a time. So maybe switching back in the right way is the most sensible alternative I see. Maybe I made a fault when trying, but I can only tell “apper” to delete cups 1.7 and install cups 1.5. If that does not work, I am done.
In the cups log I have seen these entries as you find them in the text file also some time in spring and then suddenly it stopped and now the old entries are all back and much more of them. So there was a time, when the cups fault was mended (no idea how) and now the old fault is back only much more severely.
Today apper told me, that there is a new cups update but I killed the program before it could do even more mischief.
justus_d