Comment 0 for bug 1747759

[Availability]

Already in universe

Built for all supported architectures

[Rationale]

The Common Printing Dialog Backends (CPDB) project of OpenPrinting is about separating the print dialogs of different GUI toolkits and applications (GTK, Qt, LibreOffice, ...) from the different print technologies (CUPS/IPP, Google Cloud Print, ...) so that they can get developed independently and so always from all applications one can print with all print technologies and changes in the print technologies get supported quickly.

If one opens the print dialog, the dialog will not talk directly to CUPS, Google Cloud Print, or any other printing system. For this communication there are the backends. The dialog will find all available backend and sends commands to them, for listing all available printers, giving property/option lists for the selected printers, and printing on the selcted printer. This communication is done via D-Bus. So the backends are easily exchangeable and for getting support for a new print technology only its backend needs to get added.

[Security]

No known security issues, no CVEs for cpdb-libs known.

The backends are triggered via session D-Bus and always run as the same user as the calling print dialog, so they do not introduce additional security problems.

The separation of the communication with individual print technologies makes this code only be needed once (in the appropriate backend) instead of in each print dialog. This simplifies the security maintenance.

[Quality assurance]

- The Ubuntu Printing Team is subscribed.

https://bugs.launchpad.net/ubuntu/+source/cpdb-libs
https://github.com/OpenPrinting/cpdb-libs/issues

No upstream tests or autopkgtests.

[Dependencies]

CUPS, Glib, D-Bus -> all in main.

[Standards compliance]

The package meets the FHS and Debian Policy standards (4.1.0)

[Maintenance]

- Actively developed upstream. Last release was 1.1.0
https://github.com/OpenPrinting/cpdb-libs/commits/master