Unable to create PPD file: Could not poll sufficient capability info from the printer

[madalinignisca]

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.

E [08/Oct/2024:13:20:35 +0200] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://EPSON%20XP-8700%20Series-D39FA4._ipps._tcp.local/, ipps://imprumanta-D39FA4.local:631/ipp/print) via IPP!
E [08/Oct/2024:13:20:35 +0200] copy_model: empty PPD file
E [08/Oct/2024:13:20:35 +0200] [Client 16] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/EPSON_XP-8700_Series) from localhost.

Originally posted by @madalinignisca in #308 (comment)

[madalinignisca]

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.

[zdohnal]

Hi @madalinignisca ,

what's your cups-filters version?

What gives you when you do driverless cat driverless:ipps://EPSON%20XP-8700%20Series-D39FA4._ipps._tcp.local/? Please put the complete output into file and attach file here - in general follow this point and attach the files which got created.

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.