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 ?

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

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!

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

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.

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

176

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

623

answered Jul 11 '12 at 14:19

Rinzwind

309,379

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

149

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

37,290

answered Nov 08 '12 at 09:42

ratz

1,499
1
9
2

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

114

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,335

answered Oct 01 '14 at 00:45

user249697

1,249

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

99

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,663

answered Aug 01 '14 at 11:51

sgtpep

1,107

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

39

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

59,332

answered Apr 28 '13 at 02:01

George Answerology

391

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

24

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

451

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

15

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

Nick Charney Kaye

652
7
15

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

13

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

131

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 9 · 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 9 · 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 7 · 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 5 · Answer 15 · edited Aug 02 '17 at 17:52

5

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

184

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

4

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

151

score 3 · 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

3

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

171

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

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

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

-1

remove locales using localepurge you don't need and reboot

apt install localepurge

answered Apr 09 '22 at 21:41

assayag.org

414

How do I fix my locale issue?

20 Answers20

Source of the problem

Installing

Changing/Activating

Linked

Related