How do I fix my locale issue?

Question

I am getting this message every time I do something like starting or stopping a service.

perl: warning: Setting locale failed.   
perl: warning: Please check that your locale settings:   
        LANGUAGE = "en_US:en",   
        LC_ALL = (unset),   
        LC_MESSAGES = "en_US.UTF-8",   
        LANG = "en_US.UTF-8"   
    are supported and installed on your system.   
perl: warning: Falling back to the standard locale ("C").   
locale: Cannot set LC_CTYPE to default locale: No such file or directory   
locale: Cannot set LC_MESSAGES to default locale: No such file or directory   
locale: Cannot set LC_ALL to default locale: No such file or directory   
(Reading database ... 21173 files and directories currently installed.)  
Removing bind9 ...  
 * Stopping domain name service... bind9                                        [ OK ]
Processing triggers for man-db ...   
locale: Cannot set LC_CTYPE to default locale: No such file or directory   
locale: Cannot set LC_MESSAGES to default locale: No such file or directory   
locale: Cannot set LC_ALL to default locale: No such file or directory

How do I fix this error ?

Related: [How to set locale?](http://askubuntu.com/q/17001/62483) — Lucio, Nov 06 '14 at 18:10
possible duplicate of [Locale variables have no effect in remote shell (perl: warning: Setting locale failed.)](http://askubuntu.com/questions/144235/locale-variables-have-no-effect-in-remote-shell-perl-warning-setting-locale-f) — Denilson Sá Maia, Feb 22 '15 at 19:23
Easy and permanent fix for all users: https://askubuntu.com/questions/881742/locale-cannot-set-lc-ctype-to-default-locale-no-such-file-or-directory-locale/893586#893586 — Galvani, Feb 23 '18 at 09:30
You need to say: Your machine? Or you only have a user-login and can't change system-settings? (Yeah I know this is a really old question. And the upvotes of wrong answers is appalling) — Rusi, Jan 07 '20 at 12:22

score 582 · Accepted Answer · edited Jun 28 '15 at 17:11

582

First run locale to list what locales currently defined for the current user account:

$ locale
LANG=C
LANGUAGE=
LC_CTYPE=fi_FI.UTF-8
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE=fi_FI.UTF-8
LC_MONETARY="C"
LC_MESSAGES=fi_FI.UTF-8
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=

Then generate the missing locale and reconfigure locales to take notice:

$ sudo locale-gen "en_US.UTF-8"
Generating locales...
  en_US.UTF-8... done
Generation complete.

$ sudo dpkg-reconfigure locales
Generating locales...
  en_US.UTF-8... up-to-date
Generation complete.

Now you will not see any errors anymore!

edited Jun 28 '15 at 17:11

Sheharyar

1,198
12
18

answered Dec 10 '12 at 12:45

Otto Kekäläinen

6,024
1
13
3

267

did not work for me – Umair Ayub Apr 24 '14 at 07:43
4

This has worked for me on a number of systems. Is there a way to avoid this issue on newly installed systems? – Brylie Christopher Oxley Jan 12 '15 at 17:34
13

@UmairAyub may be you have more than one unknow locale, try this: **for y in $(locale | cut -d '=' -f 2| sort |uniq );do locale-gen $y; done** It will generate a locale for each definition you have – Ivan Buttinoni Jun 27 '15 at 18:33
1

The locale in the `locale-gen` command should be in double quotes for this to work properly: `$ sudo locale-gen "en_US.UTF-8"` – Sheharyar Jun 28 '15 at 16:34
this didn't work for me in ubuntu 14.04, I'm still getting console errors. – alexserver Sep 21 '15 at 18:31
so finally I had to add export LC_ALL="en_US.UTF-8" manually in my .bachrc file. and this fixed the error prompts. But... why is that this variable wasn't configured by gen-locale ? isn't this supposed to be managed by this command ? – alexserver Sep 21 '15 at 18:37
5

Logout and Login may help – S.M.Mousavi Nov 16 '15 at 18:09
@S.M.Mousavi Tried rebooting as well, only manually exporting the variables seems to fix the issue – Prashanth Chandra Jan 12 '16 at 01:56
1

Remember open a new terminal to test it – deFreitas Jun 21 '16 at 01:57
6

@Umair There is a high risk of human error in this problem. Your system is configured to `en_GB` by default, but you set it up to `en_US`. You have to manually comment `en_GB` and uncomment `en_US` in `/etc/locale.gen`. See my answer http://askubuntu.com/a/790373/25388 in the hardware Raspberry Pi 3b and the system Raspbian Jessie. – Léo Léopold Hertz 준영 Jun 22 '16 at 20:27
Thanks. I was not able to update my softwares for so long and sometimes the operating system used to crash because of stopping the process and restarting the system – Paul Thomas Apr 17 '17 at 06:36
In fact it only worked when executing "sudo dpkg-reconfigure locales" -> select "en_US.UTF-8" from the long list (use space to select) -> Enter -> select again en_US.UTF-8 as default -> Enter. – Anonymous Apr 19 '17 at 07:24
my two cents, you might need to install `locales` first, especially if you got an error from just trying `locale -a` On Ubuntu, simply install locales by this command `sudo apt-get install locales` – Bhoom Suktitipat Dec 18 '17 at 07:55
Worked perfectly in Windows Subsystem for Linux under Ubuntu 16.04.3 LTS. Not sure how locales got broken but this fixed it. – WinEunuuchs2Unix Dec 27 '18 at 23:36
Works great!. It really helps – Thanh Hải May 13 '19 at 10:39
I had to type `159` and than `3` after running `sudo locale-gen "en_US.UTF-8"` – alper Mar 02 '22 at 09:20
This worked for me even though `/etc/default/locale` and the output of `locale` don't get changed. – Sridhar Sarnobat Aug 30 '22 at 04:58
`locale-gen` does not take any arguments, it just generates all locales that have previously been selected via `dpkg-reconfigure locales`, so it's useless here. – ggll Dec 02 '22 at 11:02

score 417 · Answer 2 · edited Dec 16 '12 at 07:56

417

Nothing suggested above worked in my case (Ubuntu Server 12.04LTS). What finally helped was putting to the file /etc/environment:

LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8

For some reason it was missing. The outputs for locale and other commands appeared like the variables were properly defined. In other words don't take for granted all the basic stuff is declared where it should be declared.

edited Dec 16 '12 at 07:56

Nicolás

269
3
11

answered Dec 16 '12 at 04:11

Marcin

4,179
1
12
3

131

Yes, none other worked except this one, perhaps due to updated version. But I rather prefer to put this in `/etc/default/locale`. – Naveed Feb 22 '13 at 20:18
30

Updated `/etc/default/locale` and no more warnings. Thanks – ohho Feb 26 '13 at 07:00
9

Yep, the others didn't work for me. This one did. Here is the one-liner I used for unattended updating of this. `sudo sh -c "echo 'LC_ALL=en_US.UTF-8\nLANG=en_US.UTF-8' >> /etc/environment"` – dman Mar 22 '14 at 06:01
16

@user163207 your solution is incorrect because it appends (instead of overwriting), it's not the recommended file, and `echo` needs to be run with the interpretation of backslash escapes enabled. This is the same as yours but with the aforementioned fixed: `sh -c "echo -e 'LANG=en_US.UTF-8\nLC_ALL=en_US.UTF-8' > /etc/default/locale"` – glarrain Apr 09 '14 at 21:22
2

I am facing the same issue in my Ubuntu Cloud Image – Umair Ayub Apr 24 '14 at 16:03
I used this method but I quoted the locale value, like ``LC_ALL="en_US.UTF-8"`` then I still got the error. Removing that quote fix the problem. – HVNSweeting Aug 13 '14 at 10:23
1

You need to log-out and log back in for these changes to have any effect. – Basil Mar 12 '15 at 13:18
1

(Old question, I know, but) LC_ALL should NOT be touched, it's an override (for all (the other) locale settings), local and remote. It means that you're, basically, forcing it (which I don't think is a viable solution :)) – Nostromov May 30 '15 at 20:25
15

DON'T FORGET TO LOGPUT AND RE-LOGIN! – S.M.Mousavi Nov 16 '15 at 18:05
This is what worked for me on a fresh Raspbian install. `/etc/default/locale` only had the LANG line without an LC_ALL line. – John Baber-Lucero Dec 22 '15 at 03:48
1

@Nostromov If I leave out the LC_ALL line, I'll continue getting errors. This is the only viable and reliable solution that works for me. Anything I should watch out for as a result of setting LC_ALL? – Prashanth Chandra Jan 12 '16 at 01:58
2

it is need exit of session and relogin – jruzafa Apr 06 '16 at 11:00
Just want to say that this works. – Ru Chern Chong Feb 01 '18 at 03:46
@glarrain To apply a partial fix on this base is dangerous: Just making it to overwrite deletes other parts of `/etc/environment`. It will work, without complaining - but may break something to be noticed much later. – Volker Siegel Apr 21 '19 at 06:30
@prasanthchandra : Where are the errors appearing? Which file have you put this in (see glarain's answer)? And fundamentally : What is output of (1) locale and (2) locale -a? – Rusi Jan 07 '20 at 12:12
1

Basically @nostromov is correct. LC_ALL should **not** be set. If things get to "working" by setting it it's a kludge – something somewhere else is broken. And remains so – Rusi Jan 07 '20 at 12:15

score 172 · Answer 3 · edited Jun 30 '15 at 10:54

172

They should disappear after issuing:

sudo locale-gen en_US en_US.UTF-8
sudo dpkg-reconfigure locales

dpkg-reconfigure reconfigures packages after they have already been installed. Pass it the names of a package or packages to reconfigure. It will ask configuration questions, much like when the package was first installed.

edited Jun 30 '15 at 10:54

Jean-Christophe Meillaud

583
4
6

answered Jul 11 '12 at 14:19

Rinzwind

293,910
41
570
710

10

I am glad my troubles a year ago helped you get this fixed ;) – Rinzwind Jul 11 '12 at 14:34
1

Shouldn't this locale be generated by default? I mean `en`, `en_AU`, `en_CA`, `en_GB` are present by default but not `en_US`? – Daniel Serodio Aug 15 '12 at 16:05
@Rinzwind Thanks a lot for your effort! I do apologize; I should have worded my question better. What I meant to ask is: Why is it necessary to reconfigure the locales package after generating new locales? Seems to me like the locales work even without `dpkg-reconfigure`. – Victor Nov 18 '12 at 11:49
Using Ubuntu 14.04, in a Docker container, so nothing was being set. Django's `makemessage` needs this. This worked perfectly! thanks. – Justin Aug 11 '14 at 18:05
I believe the `sudo` is missing. Perhaps it should be: `sudo dpkg-reconfigure locales`. This worked for me after a fresh install of Ubunty 14.10 Desktop 64-bit. – bgoodr Feb 14 '15 at 19:02
Logout and Login after above solution may help. – S.M.Mousavi Nov 16 '15 at 18:06
somehow `sudo locale-gen en_US` is required on top `en_US.UTF8`. hopefully it will solve the issue for good (after multiple Ubuntu versions) – prusswan Mar 19 '16 at 18:09
It just is the perfect solution. – Arush Salil Aug 17 '16 at 07:19
Fow AWS EC2 , this will work. – Yogesh Yadav Sep 29 '16 at 23:13
1

I realize that raspbian is out of scope here, but I thought I'd mention that I had to logout and login before `LC_ALL` was properly set. – MatrixManAtYrService Dec 29 '17 at 18:27
Thank you! This, but not the other answers, solved my problem with Ubuntu 19.10 on AWS EC2. – amitp Nov 11 '19 at 18:20

score 138 · Answer 4 · edited Nov 08 '12 at 15:59

138

Just add the following to your .bashrc file (assuming you're using bash)

export LC_ALL="en_US.UTF-8"

edited Nov 08 '12 at 15:59

devav2

35,738
17
79
82

answered Nov 08 '12 at 09:42

ratz

1,389
1
8
2

3

This sweet fix worked for me on my Amazon-EC2 image (Was running their default RHEL AMI) Thanks so much! :) – gideon Dec 01 '12 at 15:07
This one worked for me with my digitalocean's Ubuntu 12.04 image. – Inan Sep 25 '13 at 11:49
3

this fixed my problem. I have to ask a question: how come the LC_ALL was not set by the locale-gen command as other answers said above this one ? – alexserver Sep 21 '15 at 18:35
Weird, all solution above didn't work for me but this one did! After exporting `LC_ALL` I could finally use `sudo dpkg-reconfigure locales`. – sobi3ch Nov 18 '15 at 11:56
finally after trying a lot of tricks , this is the working one for me on kubuntu 14.04.3 lts . thanks! – Yunus Jan 08 '16 at 20:44
@sobi3ch And thereafter you likely don't need LC_ALL. (You should find LANG properly set after the reconfigure) ie as *temporary* hack setting it is fine. Stable long-term not. (Yeah thus is **old**. Sayin' because it's currently reinforcing a bad practice) – Rusi Jan 11 '20 at 16:19
I was using `zsh` (oh-my-zsh) but this was what finally pointed me in the right direction. `~/.zshrc` contains the lines: ```# You may need to manually set your language environment # export LANG=en_US.UTF-8 ``` Uncommenting the `export LANG` line fixed it for me with `xfce4-terminal` on Ubuntu 18.04 (in a stripped-down VM with XFCE desktop.) – hotwebmatter Jan 26 '20 at 01:21
old comment but just saved me on Ubuntu 20.04 lts :) – taiyodayo Oct 20 '21 at 14:50

score 108 · Answer 5 · edited Mar 07 '15 at 20:22

108

This is a common problem if you are connecting remotely, so the solution is to not forward your locale. Edit /etc/ssh/ssh_config and comment out SendEnv LANG LC_* line.

edited Mar 07 '15 at 20:22

warvariuc

2,285
4
26
43

answered Oct 01 '14 at 00:45

user249697

1,189
1
7
5

6

I was trying other answers, but forgot I was connecting remotely until I saw your answer. Different locales on the ssh server and client was causing the problem. – Hieu Feb 27 '15 at 06:32
2

On OSX (connecting to ubuntu) it's at `/etc/ssh_config` – Michiel de Mare Jun 03 '15 at 10:01
One-liner to do this: `sed -e '/SendEnv/ s/^#*/#/' -i /etc/ssh/ssh_config` (useful for server provisioning) – Albin Jun 16 '15 at 16:57
I couldn't set LC_ALL on the locale machine but it fixed my problem with the remote server, thanks. – Alexander Shlenchack Aug 26 '16 at 20:33
3

Probably worth noting that you have to edit the file on the local machine not the remote. – Clashsoft Jul 09 '18 at 18:08
Perfect. I tried all other answers, none of them worked for me. Thanks. – moghaddam Aug 09 '18 at 14:51
On macOS High Sierra, It's still `/etc/ssh/ssh_config`. – Jin Kwon Aug 17 '18 at 05:47
And this works for AWS EC2 instances. – Jin Kwon Aug 17 '18 at 05:48

score 90 · Answer 6 · edited Dec 04 '20 at 13:07

90

There is a command for that:

sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8

It updates /etc/default/locale with provided values.

To apply the changes, you can

source /etc/default/locale

edited Dec 04 '20 at 13:07

Katu

3,553
25
42

answered Aug 01 '14 at 11:51

sgtpep

1,017
7
3

5

This is legit! Don't forget to sign out / reload your shell, or else you won't see the changes. Don't forget to check out the approved answer for generating and reconfiguring locales. – Erik Živković Feb 08 '16 at 10:28
2

Running `locale` still doesn't show any utf values. – Cerin Apr 18 '17 at 23:00
@Cerin: Myybe, a call to `locale-gen` is missing. Before, one has to do `apt-get install locales`. – koppor Aug 16 '17 at 06:19
2

This won't change LANG for the root shell on Ubuntu 16.04, as it is overruled in /root/.profile. – Willem Dec 31 '17 at 16:44
1

`*** update-locale: Error: invalid locale settings: LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8` – alper Mar 02 '22 at 08:51
1

@alper You first need to `locale-gen "en_US.UTF-8"` and then and only then check it on `sudo dpkg-reconfigure locales` – Pablo Bianchi Jun 23 '23 at 00:09

score 36 · Answer 7 · edited Apr 28 '13 at 02:05

36

What worked for me on 12.10 was this:

apt-get install language-pack-en-base

This was after dpkg-reconfigure locales produced no results.

edited Apr 28 '13 at 02:05

Seth

57,282
43
144
200

answered Apr 28 '13 at 02:01

George Answerology

361
3
3

2

This is the best answer. It's not that my locales were setup incorrectly, but they didn't actually exist. I think this is similar to the OP's problem as well ("No such file or directory" is pretty clear if your locale *is* set right!). – Breakthrough Oct 27 '13 at 21:49
1

I was getting the OPs issue ever time i was using apt-get on Ubuntu 12.04 This solved it perfectly without having to edit any files. – Deepend Jun 10 '14 at 10:13
"language-pack-en-base is already the newest version." – karlingen Aug 10 '15 at 07:51
Logout and Login may help – S.M.Mousavi Nov 16 '15 at 18:09
Worked for me in an ubuntu `chroot` under debian. Thanks :) – Wyatt Ward Feb 18 '16 at 13:25
I'd extend the solution: you can generate a command to install all the languages currently mentioned in your locale (whatever mix it may be). Here it is: `locale|tr -d '"'|cut -d= -f2|cut -d_ -f1|sort|uniq|while read lang; do [[ $lang ]] && echo apt install language-pack-$lang-base; done` (I won't state that it's the shortest possible, but it works). – gluk47 Jul 08 '16 at 10:51
This also works on Ubuntu 18.04 LTS. – PHZ.fi-Pharazon Oct 18 '22 at 19:02

score 21 · Answer 8 · answered Sep 26 '14 at 06:51

21

Don't forget exit your SSH session (or your X11) by exiting and logging back in again. All of these suggestions didn't work for me unless I logged back in....

answered Sep 26 '14 at 06:51

Michael Galaxy

421
3
4

2

This comment should get more upvotes or atleast the fact needs to be highlighted in every answer. – ni8mr Dec 09 '16 at 14:24

Charney Kaye · Answer 9 · 2016-04-28T15:14:54.690

13

I was stuck in a weird state where my local machine is set to es and so the remote machine (via vagrant) had been provisioned in an un-handled state. Therefore, I had to use the manual export= only to facilitate a successful dpkg-reconfigure. Then the system is fine.

export LC_ALL="en_US.UTF-8"
sudo dpkg-reconfigure locales

edited Apr 28 '16 at 15:14

answered Mar 22 '16 at 18:02

Charney Kaye

622
7
15

1

Best! Due to `dpkg-recofigure` displays mojibake. – Tomilov Anatoliy Jun 28 '17 at 13:47
1

This is the only one works. – Eric Jun 09 '23 at 16:20

score 12 · Answer 10 · answered Mar 27 '13 at 03:19

12

For Ubuntu 12.10 none of the above worked except for ratzs' solution. I recommend adding this to your /etc/bash.bashrc file:

export LC_ALL="en_ZA.UTF-8"
export LC_CTYPE="en_ZA.UTF-8"

answered Mar 27 '13 at 03:19

Lovemore Nalube

121
1
2

Of all the solutions above. This is the only that worked for me. – JohnnyQ May 11 '16 at 06:56

Ajeet Khan · Answer 11 · 2016-03-03T19:02:42.370

I wrote a bash script to fix above issue.The above answers are useful but setting the locale variables by simply exporting the values in shell variable will work only for a session. I permanently solved this issue by exporting the locale variables in .bash_profile file. You can also use /etc/profile file instead of .bash_profile.

echo "export LANGUAGE=en_US.UTF-8
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8">>~/.bash_profile

Don't forget to source the .bash_profile and follow the script in easy setup.

score 8 · Answer 12 · edited Jun 17 '13 at 13:54

You can try:

export LANGUAGE=ru_RU.UTF-8
export LC_CTYPE=ru_RU.UTF-8
export LC_NUMERIC=ru_RU.UTF-8
export LC_TIME=ru_RU.UTF-8
export LC_COLLATE=ru_RU.UTF-8
export LC_MONETARY=ru_RU.UTF-8
export LC_MESSAGES=ru_RU.UTF-8
export LC_PAPER=ru_RU.UTF-8
export LC_NAME=ru_RU.UTF-8
export LC_ADDRESS=ru_RU.UTF-8
export LC_TELEPHONE=ru_RU.UTF-8
export LC_MEASUREMENT=ru_RU.UTF-8
export LC_IDENTIFICATION=ru_RU.UTF-8
export LC_ALL=ru_RU.UTF-8

where ru_RU is your country code.

score 7 · Answer 13 · edited Apr 13 '17 at 13:14

Current accepted answer is not sufficient in the troubleshoot strategy because you can have an human error. You setup your system to en_US but you have en_GB enabled in/etc/locale.gen like I had in the thread here for Raspberry Pi 3b. You should have all your used locales enabled in /etc/locale.gen.

I had en_GB.UTF-8 UTF-8 only enabled in /etc/locale.gen. I should have there only enabled en_US.UTF-8 UTF-8 because of other commands run for it. So I commented GB and uncommented US, and everything work now

masi@raspberrypi:~ $ sudo vim /etc/locale.gen

masi@raspberrypi:~ $ sudo locale-gen 
Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.

masi@raspberrypi:~ $ sudo a2enmod rewrite && a2enmod headers && a2enmod ssl
Module rewrite already enabled
Module headers already enabled
Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Module socache_shmcb already enabled
Module ssl already enabled

Now, I do not get those locale mistakes with any commands.

System: Raspbian Jessie
Hardware: Raspberry Pi 3b

score 6 · Answer 14 · edited Sep 16 '16 at 17:57

As said here in the Debian Wiki, you can edit /etc/locale.gen and add all locales (or uncomment them, I had a list of all locales but all except the one I used as comments) you wish to have support for on your system. Then, execute

sudo dpkg-reconfigure locales

to update the locales on your system. Now, all of the locales you added/uncommented in /etc/locale.gen are available on your system without any warnings.

score 4 · Answer 15 · edited Aug 02 '17 at 17:52

4

If you use KDE environment, check the setlocale.sh file in ~/.kde/env/:

$ cat ~/.kde/env/setlocale.sh 
export LANG=en_US.UTF-8
export LANGUAGE=en_US:ru:en

edited Aug 02 '17 at 17:52

Community

1

answered Feb 05 '14 at 08:36

MaximKostrikin

174
4

1

this saved my ass.... thank you! Unbelievable how many places this locale crap is being set in... and how in the world does KDE manage to screw things up by mixing my two different locales (is_IS for location, money, etc and en_EN for language into a non-existent is_EN locale)! Grmpfh. – StFS May 27 '16 at 11:05
I have been struggling with this for weeks! No other answer helped me. I couldn't even assume that KDE messes with the locale in its own way. I didn't know about the `setlocale.sh` file and not a single tutorial mentions it. – user2513149 May 28 '21 at 06:00

score 3 · Answer 16 · edited Aug 02 '17 at 17:52

3

This worked for me when I had the same problem (based on the solution provided by dman):

sudo sh -c "echo -e 'LC_ALL=en_US.UTF-8\nLANG=en_US.UTF-8' >> /etc/environment"

edited Aug 02 '17 at 17:52

Community

1

answered Aug 27 '14 at 05:21

pythonhunter

141
5

I wasn't quite sure how to add the url to the comment. @EliahKagan – pythonhunter Aug 27 '14 at 06:28
1

No problem--the date/timestamp next to a comment is what links to it directly. ...So, I've noticed [glarrain's comment](http://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue/516568?noredirect=1#comment584032_229512) (calling for `>` instead of `>>`) seems like a reply to dman's. I don't actually know which way is right or best, but if you have any insight into this you could expand this answer with more information. (You don't have to though.) – Eliah Kagan Aug 27 '14 at 06:32

score 2 · Answer 17 · edited Jan 11 '15 at 12:37

You may need to run sudo dpkg-reconfigure also for the application you have installed while "locale" settings have been invalid / not matching.

While system locale was incorrectly setup I installed vim. Later when system locale was fixed I saw a situation that vim was showing utf-8 characters incorrectly as strange symbols while nano and less were showing them correctly. Running
```
sudo dpkg-reconfigure vim
```
appeared to fix the issue after the system settings were fixed.
I also noticed the same thing as already mentioned: You may need to disconnect/reconnect SSH to make changes visible.

Jingguo Yao · Answer 18 · 2017-05-26T13:42:17.133

2

Adding the following text to ~/.profile works for me:

export LANGUAGE=en_US.UTF-8
export LC_ALL=en_US.UTF-8

I am using Ubuntu 16.04 LTS 64-bit server on Linode.

edited May 26 '17 at 13:42

answered May 09 '17 at 03:07

Jingguo Yao

151
5

score 1 · Answer 19 · answered Feb 06 '20 at 23:43

1

Source of the problem

I experienced this, logging in from one machine to another via ssh. The remote machine didn’t have the locale files, that I had on my local machine. You can either disable the forwarding of the locale from your local machine to the remote machine (in the file /etc/ssh/sshd_config remove the line AcceptEnv LANG LC_CTYPE …) or install the locale (changing it is not necessary in this case).

Installing

On Fedora, RHEL, Redhat, CentOS I used

sudo dnf install langpacks-de

for the german (de) language packs. Logged out and in and it worked.

Search for other langpacks with

dnf search langpacks-

Changing/Activating

To list available locales I used

localectl list-locales

And to set a new one

sudo localectl set-locale de_DE.utf8

answered Feb 06 '20 at 23:43

erik

657
8
16

`dnf` are not Ubuntu or *flavor* commands, how is this helpful on this site? https://askubuntu.com/help/on-topic – guiverc Sep 29 '20 at 07:59
This problem is not specifically an Ubuntu problem. I gave general instructions in the first paragraph. And then an example of how to do it on a specific distribution, where I had the problem. It is basic knowledge how to translate that to another distributions package management system. – erik Sep 30 '20 at 08:34
If you wanted to post this answer, I feel the question should have been re-asked on SE *Unix & Linux* and the answer used there, thus being on-topic. – guiverc Sep 30 '20 at 08:38
My answer is absolutely on topic. None of the answers tells what the real problem is, the source of the problem. Package installation is trivial, or should be asked in a different question. It is quite similar on all distributions, also on Debian or Ubuntu. And the rest of the solution works fine on every modern linux distribution. **And** I mentioned explicitly my distributions. Instead of complaining you could **add** the Debian/Ubuntu commands. That would be helpful. – erik Sep 30 '20 at 16:16

score 0 · Answer 20 · answered Apr 09 '22 at 21:41

0

remove locales using localepurge you don't need and reboot

apt install localepurge

answered Apr 09 '22 at 21:41

assayag.org

386
2
7

How do I fix my locale issue?

20 Answers20

Source of the problem

Installing

Changing/Activating

Linked

Related