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

lpadmin, -m everywhere and Tea4CUPS #210

Closed
debiantriage opened this issue Jul 19, 2021 · 4 comments
Closed

lpadmin, -m everywhere and Tea4CUPS #210

debiantriage opened this issue Jul 19, 2021 · 4 comments
Assignees
Labels
question General usage question

Comments

@debiantriage
Copy link

I have Debian's ippeveprinter set up: /usr/sbin/ippeveprinter -f application/pdf ippeveprinter. Its URI was obtained from the driverless utility and queue creation attempted with: lpadmin -p testq -v tea4cups:/URI -E -m everywhere. This results in

Unable to connect to ":0": Name or service not known

Is there a way round this or is it never going to be possible to wrap a backend with the everywhere model?

@michaelrsweet
Copy link
Member

@debiantriage The IPP Everywhere model only works for IPP and IPPS URIs, because the PPD is dynamically generated from the capabilities returned for the queue/printer.

@michaelrsweet michaelrsweet self-assigned this Jul 19, 2021
@michaelrsweet michaelrsweet added the question General usage question label Jul 19, 2021
@debiantriage
Copy link
Author

@michaelrsweet Colour me disappointed, but the response wasn't entirely unexpected. Thanks. Back to the drawing board!

@michaelrsweet
Copy link
Member

One possible workaround: create the queue with the real URI and then change the device URI afterwards, e.g.:

lpadmin -p myprinter -E -m everywhere -v ipp://...
lpadmin -p myprinter -v Tea4cups://...

@debiantriage
Copy link
Author

Success! The colour has changed to happy. The idea is appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question General usage question
Projects
None yet
Development

No branches or pull requests

2 participants