Bug 1811735

Summary: lpr to non-existent printer reports "lpr: No such file or directory" instead of "lpr: The printer or class does not exist."
Product: [Fedora] Fedora Reporter: Zdenek Dohnal <zdohnal>
Component: cupsAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: djast, qe-baseos-daemons, twaugh, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1811716 Environment:
Last Closed: 2020-07-21 10:52:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zdenek Dohnal 2020-03-09 16:19:34 UTC
+++ This bug was initially created as a clone of Bug #1811716 +++

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.

--- Additional comment from Zdenek Dohnal on 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 1 Zdenek Dohnal 2020-07-21 10:52:02 UTC
Since the issue is only about the correcting the error message, I'm closing it as UPSTREAM.

Reported here https://github.com/apple/cups/issues/5808 .