Bug 128054 - redhat-config-printer should allow printing to arbitrary CUPS backend
Summary: redhat-config-printer should allow printing to arbitrary CUPS backend
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-config-printer
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-16 20:15 UTC by Jonathan Reed
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:22:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jonathan Reed 2004-07-16 20:15:04 UTC
Description of problem:

redhat-config-printer should allow printing to an arbitrary CUPS
backend.  While it's true that the web interface allows you to select
any valid backend in /usr/lib/cups/backend, redhat-config-printer
should allow this too.  Additionally, queues configured via the web
interface which use custom backends show up as "Browsed Queues", which
is not really correct.  Since CUPS allows anyone to write new custom
backends, it would be nice if redhat-config-printer supported them. 
The only "options" needed in the configuration pane would be "device
name" (ie: local name) and "device uri" (ie: protocol://server/queue).
   Ideally, it would look something like the "Advanced" option that is
available in Apple's "Printer Setup Utility" (which uses CUPS) if the
user Option-Clicks on the "Add" printer button.

Version-Release number of selected component (if applicable):
redhat-config-printer-0.6.47.3.19-1

Comment 1 Suzanne Hillman 2004-07-20 21:18:43 UTC
Internal RFE bug #128256 entered; will be considered for future releases.

Comment 3 RHEL Program Management 2007-10-19 19:22:28 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Comment 4 Jonathan Reed 2007-10-19 19:40:45 UTC
Nice.  Sit on the bug for long enough, and then the product will be obsolete, so it can be easily closed as 
WONTFIX.  I am in awe of this support model.

Well, I'm happy to say this feature appears to exist (although I haven't yet tested it) in RHEL 5, so perhaps 
we finally made some progress.  Some communication might have been nice, however.


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