Comment 18 for bug 2026200

I've been using headless chromium on the cli with the --print-to-pdf parameter to generate PDF documents on Ubuntu 20.04 for well over a year.

Chromium has been invoked at:

/snap/chromium/current/usr/lib/chromium-browser/chrome

... by the Apache user, and, because APT forces the SNAP Chromium package, rather than the standard Debian package, and because the Apache user's (www-data) home directory is /var/www and not /home/www-data, one cannot invoke Chromium via Apache at /snap/bin/chromium because of the SNAP home directory requirement

It is my opinion that IF Ubuntu 20.04 LTS (supported until April 2025) is built with SNAP Core20, building a single Chromium SNAP on Core22 going forward will continue to break Ubuntu 20.04 systems

Please do not make assumptions that everyone is calling Chromium with an actual/normal user

I can confirm that this "fixes" the issue for me:

  snap refresh --channel stable/core20 chromium

Nathan Teodosio said: "...And that's why we discourage and cannot support unconfined runs."

... well, the fact that /snap/chromium/**current**/usr/lib/chromium-browser/chrome (current) is a symlink to whatever build # is the "current" suggests Chromium can/and-without-problems-should-be-able-to-be called from that path (as it has been, until someone decided to make the latest Chromium build against Core22)

That, and the fact that there's no option to revert to a previous Chromium build, is why this is "broken"

With respect, not "everyone and everything" is running on the "latest and greatest"