-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
perl: warning: Setting locale failed after migration to nixos-22.11 channel #208080
Comments
I am not sure |
FWIW I just ran into this with Empirically, it affected the machines where I had set |
Now I have the following more advanced settings which were also set with plasma UI (not declaratively). $ cat ~/.config/plasma-localerc
[Formats]
LANG=en_US.UTF-8
LC_ADDRESS=nb_NO.UTF-8
LC_MEASUREMENT=nb_NO.UTF-8
LC_MONETARY=nb_NO.UTF-8
LC_NAME=nb_NO.UTF-8
LC_NUMERIC=nb_NO.UTF-8
LC_PAGE=nb_NO.UTF-8
LC_TELEPHONE=nb_NO.UTF-8
LC_TIME=en_GB.UTF-8
useDetailed=true And I made the problem disappear by adding this in i18n = {
defaultLocale = "en_US.UTF-8";
supportedLocales = [
"C.UTF-8/UTF-8"
"en_US.UTF-8/UTF-8"
"en_GB.UTF-8/UTF-8"
"nb_NO.UTF-8/UTF-8"
];
}; Perhaps there is a way to configure my user regional settings in a declarative way that would be taken into account so that I do not have to explicitly specify |
Could you reopen this? This is IMO a breaking bug in the 22.11 release, and the entry in the release notes really isn't anywhere near clear enough about the potential for breakage. Edit: In my case, manually adding the relevant locales to supportedLocales did not fix it. I had to add the "all" entry instead. |
Thanks this works. But I wonder if my computer is now stuck in the USA and not Australia? |
Describe the bug
When and after migrating to
nixos-22.11
channel, I noticed a warning :Steps To Reproduce
Steps to reproduce the behavior:
configuration.nix
:ø
in a terminal, asroot
userø: command not found
Expected behavior
No warning should appear.
Notify maintainers
@SuperSandro2000 (related to #177318)
Metadata
The text was updated successfully, but these errors were encountered: