Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lpoption wrongly tries to fetch PPD directly from the printer #4743

Closed
michaelrsweet opened this issue Dec 3, 2015 · 1 comment
Closed
Labels
duplicate This issue or pull request already exists
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

Version: 2.0.3
CUPS.org User: hawk

Description of problem:

lpoptions -l should show the available printer options. Instead it fails with 'lpoptions: Unable to get PPD file for Printername: Not Found'. Tracing the network traffic shows that the client tries to fetch the PPD file directly from the printer instead of the print server. Of course the printer does not provide the PPD file so the request fails.

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

According to a Debian Bug Report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729713) it was introduced in 1.6.1-1 (http://cups.org/str.php?L4178). I'm currently testing cups-client-2.0.3-1.fc22.x86_64 running on Fedora (Fedora Bug Report: https://bugzilla.redhat.com/show_bug.cgi?id=1287585)

How reproducible:

always.

Steps to Reproduce:

  1. Set up printer server using IPP to access the network printer (i.e.: ipp://X.X.X.X/ipp)
  2. Set up the client /etc/cups/client.conf to access 'ServerName printerserver'. Disable local printer server on the client.
  3. Run lpoptions -l on the client.

Actual results:

[hawk@iconia ~]$ lpoptions -l
lpoptions: Unable to get PPD file for Canon_PS: Not Found

Expected results:

[hawk@denobula ~]$ lpoptions -l
Opt2CF/Cassette Feeding Unit: False *True
...

Additional info:

The problem does not seem to be new. This (old) Debian bug report describes the same problem and shows when the problematic code was introduced:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729713

The conclusion from the mentioned report is that due to the use of IPP cups thinks there is another cups server. Of course this works if you run a local cups daemon that needs to fetch the PPD from the 'real' server. In this case it mistakenly thinks it needs to fetch the PPD directly from the printer.

Removing the two lines accessing ipp:// and ipps:// device-uri directly introduced here http://cups.org/str.php?L4178 resolves the problem.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Dupe of STR #4725

@michaelrsweet michaelrsweet added P0 - Unassigned (New) duplicate This issue or pull request already exists labels Mar 17, 2016
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

1 participant