Comment 19 for bug 2026200

Nathan, thanks for the detailed followup. I'm unfortunately not in a good working state, as I introduced a typo in an environment variable used to run our functional test harness when I converted to invoking /snap/bin/chromium with `runuser` instead of a direct invocation form our vagrant user. The result was our test harness ran firefox instead of chromium :(

After fixing that issue, I'm back where I started with chromium failing to find the proper glibc library with stable or edge.

I can fully appreciate your situation regarding the core22, and I can re-confirm that the stable/core20 package does work for us with the unconfirmed command, but I knew that was never going to get a support path. That being said, I'm wondering if you have any advice on the following issues:

1. Is there any way we can influence where chromium looks for glibc to find the base 2.35? (Is this something that would be resolved if I could get /snap/bin/chromium working?)

2. I still cannot get `chromium` or `/snap/bin/chromium` to work on any of the versions, stable / edge / stable/core20. It reports the rather unhelpful `cannot open path of the current working directory: Permission denied`

Migrating to 22.04 is pretty much off the table for our situation as 20.04 is still under lts and we have a _lot_ of other dependencies to deal with. I'm also ok with opening a new ticket if you are set on keeping this one closed.

Thanks in advance!
-Marcus