Bug 201800 - cups 1.2.2 puts server hostname in all printer queue names
cups 1.2.2 puts server hostname in all printer queue names
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
http://cups.org/str.php?L1893+P0+S-2+...
:
Depends On:
Blocks: FC6Target
  Show dependency treegraph
 
Reported: 2006-08-08 17:54 EDT by Orion Poplawski
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 1.2.2-1.8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-21 12:41:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2006-08-08 17:54:18 EDT
Description of problem:

In the change from 1.2.1 to 1.2.2, the print queue names for remote queues have
the hostname in them and the short name does not work.

Previously I had:

device for angelou: ipp://wind.cora.nwra.com:631/printers/angelou
device for dali: ipp://wind.cora.nwra.com:631/printers/dali

now I have:

device for angelou@wind: ipp://wind.cora.nwra.com:631/printers/angelou
device for dali@wind: ipp://wind.cora.nwra.com:631/printers/dali

and I can no longer do "lpr -Pdali".

Submitted CUPS STR#1893 on it as well
Comment 1 Tim Waugh 2006-08-09 04:10:19 EDT
(Just including upstream bug URL:)

http://cups.org/str.php?L1893
Comment 2 Tim Waugh 2006-08-09 12:14:14 EDT
FWIW, I see this here too recently.
Comment 3 Orion Poplawski 2006-08-16 10:54:12 EDT
1.2.2-1.6 seems to not exhibit the problem, but I needed to remove
/var/cache/cups/remote.cache to clear out the queues with hostnames.
Comment 4 Tim Waugh 2006-08-16 12:07:23 EDT
There is a 1.2.2-1.7 already in the pipe-line, but I have added a bit in the
spec file for 1.8 to remove remote.cache on upgrade.  Thanks for testing.
Comment 5 Orion Poplawski 2006-08-21 12:41:02 EDT
Fixed in 1.2.2-1.8. Thanks!

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