Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 76477 - system default printer can be set in two different, conflicting places
system default printer can be set in two different, conflicting places
Product: Red Hat Linux
Classification: Retired
Component: cups (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-10-22 05:17 EDT by Robert P. J. Day
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-22 05:17:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert P. J. Day 2002-10-22 05:17:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
  according to the docs, CUPS can have a system default printer
that can be seen by running "lpstat -d".

  however, there are two ways to set this system-wide value.
the first, through "lpadmin -d" puts the default value in

  the second, by running "lpoptions -d" as root, puts the
default printer name in /etc/cups/lpoptions, and this value
overrides the one in printers.conf.

  this is confusing since root can (allegedly) set a value
using "lpadmin", yet this value is ignored if a value has
already been set via lpoptions.

  as i've heard it, this is by design.  it's very confusing.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1."# lpadmin -d printer1" to set a default printer
2."# lpoptions -d printer2" to set a different default printer
3."lpstat -d" to see the (alleged) default printer, which will
  always allow lpoptions to take precedence despite the docs
  for lpadmin which simply say that you're setting the 
  "default" printer

Actual Results:    lpoptions value always takes precedence

Expected Results:  it would be nice if CUPS understood the concept of a single
default printer.

Additional info:
Comment 1 Tim Waugh 2002-10-22 05:23:10 EDT
As I said, I won't change this since it is designed to work the way it does. 
This is something to take up with the upstream developers.

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