-
Notifications
You must be signed in to change notification settings - Fork 129
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
Unable to create PPD file: Could not poll sufficient capability info from the printer #600
Comments
The error comes when I select from the list of drivers the one with XP 8700 driverless. I selected IPP Everywhere, and I managed to add the printer, and seems to work fine. |
Hi @madalinignisca , what's your cups-filters version? What gives you when you do The driverless command runs both libcupsfilters and libppd changes, so the output should have the same result as your error. I briefly checked what is present on Arch Linux, and I saw there is not the latest CUPS release, which contains mirrored changes from libppd/libcupsfilters, so there is a chance IPP Everywhere won't work for you either. Hopefully with ipptool.attr file you'll provide we can be able to mimic your printer and figure out which attribute causes this - so either your device really contains invalid values and we have not caught this till this day (which will require you reporting to manufacturer and ask for firmware update), or there is an issue within our validation logic. |
Hello, I got similar issue after updating to the latest CUPS drive on Fedora 41 with a HP OfficeJet Pro printer. That will update /etc/nsswitch.conf with the following profile
Then install the printer as usual. Full details from Fedora Magazine. |
I am getting this error today, reported in 2020 #308.
Probably since one of last updates of packages.
I use Arch. The printer worked until recently, no issues. Even tested occasionally by removing it and adding it back.
I think it happened since the update with the recent CUPS security issue.
Originally posted by @madalinignisca in #308 (comment)
The text was updated successfully, but these errors were encountered: