Comment 26 for bug 2026200

> (I still maintain that if Ubuntu 20.04 LTS is supported until April
> 2025, and its base SNAP is core20, it is not appropriate (if, only
> because of my biased opinion) to build snaps on core22, which, you
> admit, is the base snap core for Ubuntu 22.04)

I think there is a misunderstanding here. Snaps for core22 can run in
any series, be it 18.04, 20.04, 22.04 etc., otherwise it would really
mean that for each series XX we would have to use the corresponding coreXX.

They can only run in any series because they are not run directly as a
binary that sees the host libraries, but rather uses snap confinment. So
if your base is 20.04, a snap based on core22 works nonetheless, because
it's seeing the libraries provided by core22 instead of your host system.

That is _exactly_ what is sidestepped once you run it with the
/snap/chromium/current/usr/lib/chromium-browser/chrome instead of the
normal /snap/bin/chromium, namely the snap runs unconfined an thus uses
the system libraries, which may be (and in the present case is)
different than what it was linked it during its build, justifying the
errors you see.

> Do you have any sense of "how long" the stable/core20 channel will be
> available?
>
> I am grateful for the stable/core20 build as of now, but need to plan to either migrate to Ubuntu 22.04 (or later) or off Ubuntu altogether

By default it's 30 days after launch, I'm happy to keep it alive for
longer though if it will help, just note it is frozen, it will not be
maintained, so new CVEs in Chromium or any of its dependent libraries
won't be addressed and so on.