IPP is NO match for Appsocket/Jetdirect with PPD

[kvsrikantha]

Cups Version: 2.4.7
OS: Ubuntu 24.04
Printers: Konica Minolta Bizhub 754e and Bizhub 958

Capabilities of printers: High speed, Monochrome with Stapler and Saddle Stitch unit.

History: For many years now I was using "lpadmin -v socket://IPAdress:9100 -P PPDfile". Cups was able to install printer smoothly. I had created printer instances for duplex, stapled and booklet finishing separately. Absolutely no problems.

Modernity: "lpadmin -v ipp://IPAdress:631/print -m driverless:ipp://...". Also tried "-m everywhere". These do NOT detect full capabilities of the printer like stapling, booklet finishing. Years of functionality with this beast of a printer is now broken.

Question: Is there no way to maintain the smooth experience with printers, the way one had with PPDs with IPP?

I have attached the results of running lpoptions -l on the two ways of installing KM 958.

OPTIONS detected by APPSocket.txt

OPTIONS detected by IPP.txt

[dkosovic]

You are using OpenPrinting CUPS 2.4.7, the latest version of Apple CUPS is 2.3.3. The OpenPrinting CUPS issues page is probably the best place to submit the issue:

• https://github.com/OpenPrinting/cups/issues

My workplace has multiple Konica Minolta printers, I had to enable AirPrint and Mopria in the printer's settings for IPP Everywhere to pickup missing features. I had an issue with StapleLocation not working, had to set the default on the printer to None before it would use user specified values.

The as of yet unreleased OpenPrinting CUPS 2.5 will still support PPDs, then with CUPS 3.0 that comes after that, you can use pappl-retrofit for legacy PPD files:

• https://github.com/OpenPrinting/pappl-retrofit

[dkosovic]

Forgot to mention, a fairer comparison might be to compare the IPP attributes (as opposed to PPD attributes) between printer, CUPS queue using IPP and CUPS queue using AppSocket, e.g.:

For printer IPP attributes:

/usr/bin/ipptool -t -v ipp://xxx.xx.xxx.xx/ipp/print  get-printer-attributes.test

For a CUPS print queue:

/usr/bin/ipptool -t -v ipp://xx.xxx.xx.xxx/printers/queue  get-printer-attributes.test

On a KM C450i it has all of the finishing options, pin password and more. not sure about KM 958. Also don't have to deal with the proprietary PPD options that have a KM prefix that don't map too well like KMDuplex in user interfaces.

[kvsrikantha]

Dear Douglas, Thank you for your detailed and helpful response. Will check it out!

…

On Fri, 6 Sept, 2024, 1:42 pm Douglas Kosovic, ***@***.***> wrote: Forgot to mention, a fairer comparison might be to compare the IPP attributes (as opposed to PPD attributes) between printer, CUPS queue using IPP and CUPS queue using AppSocket, e.g.: For printer IPP attributes: /usr/bin/ipptool -t -v ipp://xxx.xx.xxx.xx/ipp/print get-printer-attributes.test For a CUPS print queue: /usr/bin/ipptool -t -v ipp://xx.xxx.xx.xxx/printers/queue get-printer-attributes.test On a KM C450i it has all of the finishing options, pin password and more. not sure about KM 958. Also don't have to deal with the proprietary PPD options that have a KM prefix that don't map too well like KMDuplex in user interfaces. — Reply to this email directly, view it on GitHub <#6214 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE47P5NBCX2CR6RQR3TRBODZVFPWTAVCNFSM6AAAAABK4MJQHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGQ4TMMZTGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>