New newbie problem: CUPS printing "job-stopped"

Hi again!

Another newbie problem here: I had bought a Canon PIXMA MP160
multi-function printer/scanner a couple weeks ago. I got the printer
more or less working (sadly only capable of 600x600 resolution with the
MP150 driver in CUPS/Gutenprint), and couldn't get the scanner working.
Then my 6-year-old son decided to shove a piece of cardboard through the
paper slot and it stopped working completely. I took the thing back, and
the only thing the store would let me do without dropping more cash was
to exchange it for the exact same model. I brought that home and tried
it out.

It seemed to work, and then through trial and error I got the scanner
part to work. But now, every time I try to print, nothing happens. CUPS
reports "printing: job-stopped" and says the printer is "Ready". I've
looked in various places online to find info. Apparently, this is a
pretty common problem. But none of the suggestions I've tried work.

I'm using Debian Etch PowerPC GNU/Linux, and I've tried updating
CUPSYS, Gutenprint, and Foomatic to the newest versions I can find in
the Debian repositories (in Testing, not Unstable) as suggested in one
forum post. I'm stumped and frustrated because I have to be able to
print! Any ideas (besides throwing out either the printer or the OS -
both of which I've considered lately)? Thanks!

Mike Freeman
mike [at] freeman-studio [dot] com

On Sat, 01 Sep 2007 21:07:43 -0700,
Michael and Nicole Freeman <mnfreeman@cox.net>, in
<kGqCi.29601$L_7.22004@newsfe16.phx> wrote:
[color=blue]
>+ I'm using Debian Etch PowerPC GNU/Linux, and I've tried updating
>+ CUPSYS, Gutenprint, and Foomatic to the newest versions I can find in
>+ the Debian repositories (in Testing, not Unstable) as suggested in one
>+ forum post. I'm stumped and frustrated because I have to be able to
>+ print! Any ideas (besides throwing out either the printer or the OS -
>+ both of which I've considered lately)? Thanks![/color]

Don't do either. What you're encountering is the default CUPS
behaviour when it thinks it can't talk to the printer: it shuts down
the queue.

One way to solve it is to renable the queue:

# cupsenable <queuename>

But once you've done that, oh, 3 times, it gets annoying. A more
permanent fix is to change the default behaviour. As root, goto
/etc/cups/

and modify "printers.conf". Search on the string ErrorPolicy and
change that line to read:

ErrorPolicy retry-job

instead of the default, which is:

ErrorPolicy stop-printer

Now, if there is acutally a connection problem, well, the job won't
print. But you can come back and ask questions about that later.

--
Consulting Minister for Consultants, DNRC
I can please only one person per day. Today is not your day. Tomorrow
isn't looking good, either.
I am BOFH. Resistance is futile. Your network will be assimilated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG3UzRVcFcaSW/uEgRAvu4AJ91zSmZjhTtOVUPEnRd0Lq0js3ljACfSOUf
R5Xrj903BCvsAEJhT17SXWo=
=7Ff0
-----END PGP SIGNATURE-----

On Tue, 04 Sep 2007 13:17:17 +0100,
Roger Leigh <rleigh@whinlatter.ukfsn.org>, in
<871wdesjzm.fsf@hardknott.home> wrote:
[color=blue]
>+ I R A Darth Aggie <n0b0dy@192.168.10.10> writes:[/color]
[color=blue]
>+ > ErrorPolicy stop-printer[/color]
[color=blue]
>+ Note you can also set this in the web interface on a per-printer
>+ basis without having to touch cupsd.conf.[/color]

Yes, yes, that's all well and good. But I can never remember where to
find the silly thing in the web interface. By the time I can remember
where, I could have solved the issue with some quick editing.

But what can I say? I'm just a command-line luddite.

;-)

--
Consulting Minister for Consultants, DNRC
I can please only one person per day. Today is not your day. Tomorrow
isn't looking good, either.
I am BOFH. Resistance is futile. Your network will be assimilated.

I have a similar problem when my printers run out of paper. However, adding errorpolicy retry-job fixed the problem temporarily. Cups will overwrite your printers.conf file eliminating the errorpolicy retry-job entry. I am using Redhat ES 4.0. Any suggestions?