For a quicker solution one possibility could be to go through the xdg-
desktop-portal, the way how Flatpaks print. Here one should perhaps
investigate the Flatpak of Chromium and see how printing in it works,
whether the Chromium print dialog is patched there to make use of the
portal or perhaps completely suppressed so that Chromium is forced to
use the system's dialog which would make it using the portal.

It is important to know that Chromium has its own print dialog, it is
not using the standard GTK dialog by default.There is a link/button in
Chromium's print dialog so that you could use the "system's" print
dialog, and then it opens the GTK dialog, so one could probably easily
patch Chromium to use the GTK dialog (and so also the portal) right
away.

Looking at the syslog messages in the bug report, Chromium's print
dialog seems to directly access the PPD files in /etc/cups/ppd/, which
is already against the principles of using CUPS (there are CUPS APIs to
obtain the printer capabilities). This direct access is not possible
with the browser being snapped.

So a dirty workaround could be adding something like this to Chromium's
snapcraft.yaml:

-----

plugs:
  etc-cups:
    interface: system-files
    read:
      - /etc/cups

-----

This way Chromium in the Snap would be allowed to read the PPD files and
so it would work without patching Chromium or sacrifying Chromium's own
print dialog by configuration, but on the other side I am not sure
whether this interface would need permission from the Snap Store team
for auto-connection.

At least it only allows to access CUPS's  configuration and not any
spooled jobs or history, so it does not open up too much of the user's
privacy (and it could be more restricted, only allowing access to
/etc/cups/ppd instead of /etc/cups).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088333

Title:
  Chromium - printer unavailable - apparmor denial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2088333/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to