With this thread I request auto-connection of the host system’s “cups-control” interface by the CUPS Snap (“cups” in Snap Store).
In the CUPS Snap there is one app named “cupsd” to run the CUPS daemon. The CUPS daemon can be run in standalone mode (Snap’s CUPS is the default printing environment), parallel (independent CUPS daemons of Snap and hos system, for development only), and proxy mode (Snap’s CUPS is a proxy for the system’s CUPS, to protect the system’s CUPS against administrative requests from the client).
In the proxy mode the Snap’s CUPS needs a clone of each queue on the system’s CUPS. The cloning is done by the auxiliary daemon
cups-proxyd, also running as part of the “cupsd” app, and
cups-proxyd knows about changes by DNS-SD notifications from network printers and D-Bus notifications of local (USB, socket, non-IPP) CUPS printers. For
cups-proxyd (inside the CUPS Snap) subscribing to the system’s CUPS’ (outside the CUPS Snap) D-Bus notification service it need appropriate access to the system’s CUPS and therefore the “cupsd” needs to plug the system’s “cups-control”.
Therefore I want to request auto-connection to “cups-control”.
See also here.