Comment 15 for bug 2026200

To be clear, the reason why this has hit you is that Chromium in the stable channel switched from Core20 in 114.0.5735.106 to Core22 in 114.0.5735.198 (this is a downstream, in other words Ubuntu maintainer's, decision, not Chromium's maintainers').

Core20 is a base from Ubuntu 20.04, while core22, from 22.04.

As such, it makes sense that you had no library problems in Focal with the unconfined command (/snap/chromium/.../chrome) when Core20 was used — as the base and your system libraries were the same, they were compatible environments.

Once Core22 is used to build, Chromium is linked against its libraries, and if you run the unconfined command in 20.04 now, it will find the host's GLIBC 2.31 instead of the base's 2.35; That aligns with the error messages.

And that's why we discourage and cannot support unconfined runs.

We are not tempted to switch back to Core20 — unless issues with the supported run (/snap/bin/chromium, snap run chromium or simply chromium) are found — because Core22 is the newer base, and actually solves bugs with hardware acceleration.

I created the stable/core20 channel with the previous snap so you, the affected users, could confirm the switch was the cause and have time to adapt. But very importantly: This does not mean that we are going to actively maintain that new channel, so please don't rely on it for long term.