Bug 9779 – Printer running out of paper jams entire queue

Bug 9779 - Printer running out of paper jams entire queue

Summary:	Printer running out of paper jams entire queue

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lpr (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-02-25 10:02 EST by Ken Crandall
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-25 13:00:27 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ken Crandall 2000-02-25 10:02:49 EST

When a local printer runs out of paper, the queue jams and all other
printers are unable to print unless the LPR daemon is restarted.

Configuration:

Epson-Compatable local printer on /dev/lp1
Several serial printers on /dev/ttySx (connected via Stallion multi-port
serial card.)

The configuration was tested as boot root and in userspace.

Comment 1 Ken Crandall 2000-02-25 13:00:59 EST

Additional Information:

The isolation problem only occurs when the machine is rebooted with a job in the
queue (in other words, printing on all printers still continue even when one of
the other printers encounters an error).

This would seem to indicate that local printers are being handled differently
than net printers as far as queue processing is concerned...

Comment 2 Bernhard Rosenkraenzer 2000-07-17 11:18:00 EDT

This is fixed in rawhide with the move to LPRng.

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