Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1811716 - lpr to non-existent printer reports "lpr: No such file or directory" instead of "lpr: The printer or class does not exist."
Summary: lpr to non-existent printer reports "lpr: No such file or directory" instead ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cups
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: 8.0
Assignee: Zdenek Dohnal
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1811735
TreeView+ depends on / blocked
 
Reported: 2020-03-09 15:37 UTC by Dan Astoorian
Modified: 2020-03-09 16:19 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1811735 (view as bug list)
Environment:
Last Closed: 2020-03-09 16:18:41 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

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.


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