Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 163960 - cups classes failover doesn't work
Summary: cups classes failover doesn't work
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: cups
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
Blocks: 234011
TreeView+ depends on / blocked
Reported: 2005-07-22 13:45 UTC by Bastien Nocera
Modified: 2018-10-19 20:57 UTC (History)
2 users (show)

Fixed In Version: RHBA-2007-0475
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-06-11 18:37:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:0475 normal SHIPPED_LIVE cups bug fix update 2007-06-07 20:23:14 UTC

Description Bastien Nocera 2005-07-22 13:45:36 UTC
After configuring two printer as a class, schedule 10 printjobs one page each.

1-2 minutes before printing pull the plug on say printer 2.

Start printing 1st job get sent to printer 1 and print second job gets sent to
printer 2 which is not there

It doesn't print as printer 2 isn't plugged in and sits there waiting. All the
remaining jobs getting sent to printer 1.

The problem is acknowledged upstream:

Comment 1 Tim Waugh 2005-07-22 13:53:28 UTC
Judging from the upstream reaction, I guess Red Hat Enterprise Linux 4 is
affected too.

Comment 9 Red Hat Bugzilla 2007-06-11 18:37:45 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.