Bug 1811716

Summary:	lpr to non-existent printer reports incorrect error
Product:	Red Hat Enterprise Linux 8	Reporter:	Dan Astoorian <djast>
Component:	cups	Assignee:	Zdenek Dohnal <zdohnal>
Status:	CLOSED ERRATA	QA Contact:	Petr Dancak <pdancak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.1	CC:	bmason, pdancak, soutteri
Target Milestone:	rc	Keywords:	AutoVerified, Patch, TestCaseProvided, Triaged
Target Release:	8.0	Flags:	pdancak: needinfo+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cups-2.2.6-41.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1811735 (view as bug list)		Environment:
Last Closed:	2022-05-10 15:21:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Astoorian 2020-03-09 15:37:14 UTC

Description of problem:
When using lpr (or lp) to print via CUPS from the command line, specifying a nonexistent printer name results in a delay of 1 to 2 seconds, followed by the message "lpr: No such file or directory".

Version-Release number of selected component (if applicable):
cups-2.2.6-28.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run:
  lpr -Pfake /etc/resolv.conf
(where "fake" is not the name of a configured printer).

Actual results:
The message "lpr: No such file or directory" is produced after a short delay.

Expected results:
The message "lpr: The printer or class does not exist." should be produced immediately.

Additional info:
"lp -dfake /etc/resolv.conf" produces the same result.

Comment 1 Zdenek Dohnal 2020-03-09 16:18:41 UTC

Hi,

Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:
    https://www.redhat.com/support/process/production/#howto

I'll clone the bugzilla to Fedora.

Comment 4 Zdenek Dohnal 2021-11-03 05:17:00 UTC

Reopening this ticket per request from the regular Red Hat support channels.

Comment 19 errata-xmlrpc 2022-05-10 15:21:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (cups bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2032