For you the snapped CUPS daemon is running, not the one of the Debian package. This means that principally you can print, especially as your printer is driverless. Printer setup tools like system-config-printer and KDE Print Manager can communicate with the CUPS daemon normally. You only would see a difference if you go through the "Add Printer" wizards of system-config-printer and KDE Print Manager and do not see the usual choice of thousands of printer models/drivers.
The problem that non-GNOME applications are able to communicate with CUPS and you can print with them but GNOME application fail to correctly communicate with CUPS seems to be the same, both for CUPS from Debian packages and for CUPS from the Snap. Somehow it seems that your `systemctl mask ...` calls do not get undone by the `systemctl unmask ...` which is not according to the man page of `systemctl` and this way the newly installed CUPS from Debian packages does not start again and the snapped CUPS therefore takes the role of the system's print service. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2083530 Title: gnome-control-center not able to add printer or make settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2083530/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
