[SOLVED] Zsh prompt problem/error after update

[daniloquispe]

Hello:

I have the same problem (I updated my system via sudo pacman -Syu last night). Tried this solution, but after running sudo locale-gen nothing happens:

Generating locales...
Generation complete.

Then I checked on “Language & region” option in GNOME Shell configuration, and language list (with default set to Spanish before update) is now empty!

How can i recover my language list?

[Hanzel]

Welcome to the forum @daniloquispe

Consider subscribing to the Stable Updates Announcements RSS feed

Check out the guide below, you need to find the right locale for spanish in
/etc/locale.gen remove the # before the line that you need and then run sudo locale-gen There are more options them I em used to, you probably just need one line un-commented.

[root tip] Troubleshooting locale errors

Difficulty: ★☆☆☆☆ Locale Errors Locale errors are not always obvious and some applications simply stop working without any hints at all - e.g. Gnome Terminal is very sensitive to incorrect configuration of locale. TL:DR As root edit the file /etc/locale.gen Enable the needed locales - including en_US.UTF-8 UTF-8 as fallback. Rebuild the locale database using the locale-gen script The Calamares installer adds the locales chosen to the end of /etc/locale.gen so check the bottom of the file be…

[linux-aarhus]

• [Stable Update] 2021-02-09 - Kernels, Gnome 40-Alpha, KDE Apps 20.12.2, Systemd, Mesa, LibreOffice - #2 by philm
• [root tip] Troubleshooting locale errors

[Nachlese]

You tried which solution?
This one?

@pablomhr

Use this command in the terminal
sudo echo en_US.UTF-8 UTF-8 > /etc/locale.gen && sudo locale-gen

He (or you) should have taken more care and should have written this instead:
sudo echo en_US.UTF-8 UTF-8 >> /etc/locale.gen && sudo locale-gen

Then you’d still have your locale file.
Now you have one which only contains US english.

See if you still have it:
sudo nano /etc/locale.gen
uncomment the locale you want (remove the hash mark → #)
then run:
sudo locale-gen

[daniloquispe]

Solved!

The "uncomment line in /etc/locale.gen worked. Thanks @Hanzel and @Nachlese!

But this is still weird for me… I have a second PC with Manjaro (laptop), also with “Spanish (Peru)” language set. I didn’t update system yet, and I checked /etc/locale.gen file and all lines in file are commented. So, why is my Spanish language configuration working fine in my laptop (non-upgraded) but lost in my mail PC (just upgraded)?

[Hanzel]

Glad you are up and runing again

@daniloquispe

But this is still weird for me… I have a second PC with Manjaro (laptop), also with “Spanish (Peru)” language set. I didn’t update system yet, and I checked /etc/locale.gen file and all lines in file are commented. So, why is my Spanish language configuration working fine in my laptop (non-upgraded) but lost in my mail PC (just upgraded)?

I’m not able to explain that situation, but when you have the same issue, you know what to do to fix it.

[daniloquispe]

Well, that’s right. At least I learned a new trick today, hehe

Thanks again!

[Nachlese]

It probably has been replaced/overwritten - well, not probably, but rather: obviously
… which shouldn’t have happened.

As soon as the package “glibc” is updated, the command “locale-gen” is run.
If the file is pristine - like new, with everything commented - you’ll lose your locale setting in that moment.
… check that file in your other computer and uncomment what you need so the next update of glibc will not harm you
perhaps make a backup of that file
sudo cp /etc/locale.gen /etc/locale.gen.original

Why this happened? I don’t know.
But it hit many - the forum is full of it.