Comment 4 for bug 2026200

Sure thing, I can provide any information you need.

1. Happened with the latest update to Chromium, has been working fine for over a year. I use it for functional testing in combination with selenium and facebook webdriver. Have it installed as a snap, so I presume it was auto updated, but I do not have a previous install listed so I cannot revert.

2. Running chromium from the terminal in headless mode produces the same series of GLIBC errors as posted by @Dalik.

```
/snap/chromium/current/usr/lib/chromium-browser/chrome --headless --disable-gpu --disable-software-rasterizer
/snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
/snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
```

If I run chromium without the qualified path I get a permission denied issue, regardless of sudo/--no-sandbox.

Dev environment is ubuntu 20.04 running on a macbook pro in a virtualbox vm.

We also have this exact same issue on our CI server which is an ubuntu 20.04 server on aws. I'm booting that up to see if snap reports any previous versions, but we get the exact same error on that server too.