Comment 20 for bug 2026200

Am 07/07/2023 um 17:59 schrieb Michaelus:
 > ... 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

That is LP:1620771.

 > 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

That invocation is not supported, so one could argue that it breaks
unsupported setups. I say that although I appreciate that as per
LP:1620771 that might currently have been the only way for you.

 > ... 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's unfortunate because, in general, it cannot. Please feel free file
a bug against snapd if you believe that should change, this one is mixed
up with printing so it wouldn't be proper to target it to snapd as of now.

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

There is, as for all snaps, with "snap revert", but that is indeed not
at all a solution.

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

Sure, and I'm glad no one here holds that opinion.