-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snap-based apps wrongly gripe about locale, etc. #22
Comments
Mmm... but why your LANG environment variable is "C" instead of "en_US.utf8? In my system, "locale" returns LANG=es_ES.UTF-8 and 'env | grep -E '^LC_|LANG=' returns LANG=es_ES.UTF-8 |
I don't know and it doesn't matter. I get the same result if LANG is unset, or if it's set to en_US.utf8.
And the very first time I run Chromium after a reboot and login, it's even worse:
|
Mmm... the odd thing is that those "Permission denied" come from inside bashrc... That sounds a little bit like there is something that you set in your bashrc that dislikes being executed inside an snap... |
It has nothing to do with the contents of .bashrc. I get the diagnostics even if temporarily replace .bashrc with an empty file:
The problem is that I am setting my ENV and BASH_ENV environment variables, which Bash users are allowed to do:
but snapd is disallowing access to my .bashrc. If snapd wants to disallow BASH_ENV etc, it shouldn't be passing BASH_ENV to the commands it runs on my behalf. |
Ooook... that makes sense now. |
But then this bug doesn't belong here... I'll comment it to the snapd people. |
I am running Ubuntu 22.04.1 LTS on x86-64 with current patches. I am using snapd 1.60-0ubuntu1.
When I run the shell command "chromium --version" and attempt to debug the resulting situation a bit, I see the following. As you can see, I get a bogus diagnostic about the locale and about my .bashrc. My locale is fine, although evidently snap packages can't use it. My .bashrc is quite simple and has not changed in two decades (it's mode -r--r--r-- which is evidently what snap is complaining about, but that has always worked fine with Bash).
I see similar problems with Firefox and with snap-store, so this is not just a Chromium issue:
Once (just after a long idle period in my login session) it was even worse:
I have filed Ubuntu Bug #1983399 and Bug #1959845 about the locale and .bashrc problems; they suggested that it was an upstream problem and that I file a bug with you. I just now observed the update.go issue and have not filed a bug report with Ubuntu about that.
The text was updated successfully, but these errors were encountered: