Comment 6 for bug 1961791

Other trivial workaround: keep snapd to 2.44.3 (at least on 20.04), possibly forever. There's a serious QA problem here, in a week I got three updates, each of which progressively broke stuff worse than the previous one:

- first warnings every time I opened a shell
- then broken XDG env, which made applications crash in the strangest ways but only when started from the shell
- then even more broken XDG env that literally _broke the user session after login_.

I don't think a bug can get worse than this, as it makes the machine (progressively more) impossible to use _for tasks unrelated to those for which you need this package_, and, with the exception of the first problem, without any hint about the fact that it's snapd fault — in the last case I only suspected that (and downgraded) because I was bit by the first issue, I had to debug the second one, and it dawned on me that they could have fucked up the fix for a third time after managing to open a shell inside the broken session through strange expedients and checking the environment.

I get that the Linux desktop environment initialization is a shitshow, but after breaking this for the first time the response should have been immediate rollback and _thorough_ testing instead rushing fixes, at least on the LTS channel.