Running openSUSE Tumbleweed (snapshot 20151115)

Connected directly via USB

Output to printer through enscript.

Sample attempts:

Case 1
Using Driver: M332x.ppd v 1.2
Make and Model: Samsung M332x 382x 402x Series PS
Output of 9 page job is perfect until the bottom of the 8th page.
Stops while reporting on screen the 9 page job is completed.

Case 2
Using Driver: POSTSCRI.PPD v 1.1
Make and Model: Samsung M332x 382x 402x Foomatic/Postscript
Output of same 9 page job is perfect until the bottom of the 7th page.
Stops while reporting on screen the 9 page job is completed.

Another file picked at random for printing, this one of 28 pages.
Again, and on both of the above drivers, everything was fine until the printer just stopped in its tracks at the bottom of the 19th page.

Badly in need of a bit of a leg-up here if someone can set me on a more productive path.

My thanks for taking the time to read this ....

George

If you print to file first (as PDF), then print the resulting multi-page PDF, does that complete successfully?

If you print the 'problem' documents a few pages at a time by breaking the print job up, does that fail at any stage?

The CUPS /var/log/cups/error_log file is useful to examine when having issues like this. It might help determine where in the processing chain things are going wrong. It may be that a bug report is required.

If you feel like getting in deep and dirty, then this (Fedora-based) How_to_debug_printing_problems guide can show you how to run the CUPS filters by hand, allowing you to examine the output data at each step as it is converted between different formats. It's not a trivial exercise, but is the kind of steps needed to locate where the processing might be failing.

1 members found this post helpful.

Well, ferrari, you did provide the focus I needed to narrow down this month-long mess.

I followed along by

First, converting an ascii file (actually /usr/lib/sendmail.d/update) to 'output.ps'
Then, creating output.pdf from output.ps with evince.

As expected, the print run finishes (at least in its own mind!) without crossing the ribbon,
but evince gives me the opportunity to complete a printing job when I need, and need it I will
because sendmail is next up on my bucket list.

To avoid confusion, I cleared out the /var/log/cups/error_log file before removing and adding a printer.
There is nothing in the log after the printer was started up. However, the printer came alive some 3-4 minutes
later and eeked out another page. That was an hour ago, and still nothing reported in the log file. The queue,
of course, is empty.

That puts the spotlight on the Samsung unit. I have zero tolerance for anything made in China,
(which means virtually everything digital at least in the consumer world) and
unless I am missing something in the Tumbleweed distribution, the printer is headed to the the dumpster
after 4 weeks of unreliable service.

On a personal note, the last major holiday I have had was 2 months in NZ over Christmas 1986/87. Lots of
fond memories. In many ways, NZ is a 'concentrated Canada'. And in my hallway is a fave photo I took at the heli
landing site before we rode up to the Fox glacier. I'll never look at that picture quite the same way again after
last week.

Thanks for helping me resolve the print problem. I switched to Tumbleweed last spring when Fedora broke its distros
into pieces. Now, I have to wonder what took me so long ;-)

George