Mailinglist Archive: opensuse-bugs (7195 mails)

< Previous Next >
[Bug 481794] CUPS print job stalled after suspend/resume
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 4 Mar 2009 03:03:41 -0700 (MST)
  • Message-id: <20090304100341.B164FCC7D5@xxxxxxxxxxxxxxxxxxxxxx>

User jsmeix@xxxxxxxxxx added comment

Johannes Meixner <jsmeix@xxxxxxxxxx> changed:

What |Removed |Added
Resolution| |INVALID

--- Comment #1 from Johannes Meixner <jsmeix@xxxxxxxxxx> 2009-03-04 03:03:41
MST ---
Disrupting an active print job this way can cause
arbitrary results depending on the particular CUPS backend
(usb, parallel, socket, lpd, ipp, ...) and the particular state
when the suspend hits the backend and the filters.

A disrupted print job can usually not be resumed at all
because it is usually not possible to re-set the printer
in the exact state when the disrupt happened.

In this particular case a resume does not make sense
because this would mean to block the printer until
the computer is resumed (i.e. one client system which
is suspended would block the whole printer until
the particular client-system is resumed).

The default ErrorPolicy in cupsd.conf is "stop-printer"
which results that the queue is disabled, see

You should try out if another ErrorPolicy works better.
For your particular case I would try "abort-job".

I don't think that disrupting an active print job this way
is supported at all by the current CUPS version so that
I close the report as invalid for the current CUPS version.
I assume that currently all you can do is to wait until
the print job is sent to a remote queue or until locally
active print jobs are finished.

I will ask on cups@xxxxxxxxxx how suspend and resume is
suppoded to work with CUPS.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >