Bug 100796 - Please support IPP print queues
Please support IPP print queues
Status: CLOSED DUPLICATE of bug 82892
Product: Red Hat Linux Beta
Classification: Retired
Component: redhat-config-printer (Show other bugs)
beta1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-07-25 12:00 EDT by Dax Kelson
Modified: 2007-04-18 12:56 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:57:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dax Kelson 2003-07-25 12:00:24 EDT
Description of problem:

IMO, the two ubber cool things about CUPS is the PPD file support and IPP.

Please enhance redhat-config-printer so that you can create a local queue that
is connecting to a remote IPP queue.

I added to two remote IPP printers using the lpadmin command, then when I ran
redhat-config-printer, I received these messages on standard out/error.

Can't understand DeviceURI: http://n2125.gurulabs.com:80/ipp/
Can't understand DeviceURI: http://phaser860.gurulabs.com:80/ipp/

When I then added a remote LPR printer via redhat-config-printer, I now had two
entries in the /etc/cups/printers.conf file that both claimed to be DefaultPrinter.

This would cause CUPS to crash on start.
Comment 1 Tim Waugh 2003-07-28 06:01:06 EDT

*** This bug has been marked as a duplicate of 82892 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:57:44 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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