Hot answers tagged

260

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 ...


195

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 ...


134

check which locales are supported: locale -a add the locales you want (for example ru): sudo locale-gen ru_RU sudo locale-gen ru_RU.UTF-8


114

That's because your locale in your local machine is set to German, which SSH forwards to and tries to use on the server, but your server does not have it installed. You've got several options: Generate the locale. Generate the German locale on the server with sudo locale-gen de. Stop forwarding locale from the client. Do not forward the locale environment ...


94

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.


67

I had the same problem, but found the following solution over at ubuntuforums: export LANGUAGE=en_US.UTF-8 export LANG=en_US.UTF-8 export LC_ALL=en_US.UTF-8 locale-gen en_US.UTF-8 sudo dpkg-reconfigure locales


64

Just add the following to your .bashrc file (assuming you're using bash) export LC_ALL="en_US.UTF-8"


46

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.


42

Here's another solution, also from Ubuntu Forums. I think this is somewhat cleaner and more robust: it doesn't involve customising Ubuntu's locale files (only settings that you're supposed to edit). Gnome calendar applet adheres to your locale settings. In Ubuntu, you can assign locale components by editing the file /etc/default/locale. Here is ...


34

click on system settings. Click on Language Support. Click on the Regional Formats Tab, and change language to English, and apply system- wide. and that will do it. Note: You may have to reboot, so changes can take effect


32

check which locales are supported : less /usr/share/i18n/SUPPORTED Add locale to list of generated echo ru_RU.UTF8 >> /var/lib/locales/supported.d/local Regenerate list (it will invoke locale-gen...) sudo dpkg-reconfigure locales


31

Usually this error means that you could have been changing between different languages (locales) and something has caused this to error erroneously. You could try regenerating your list of locales with sudo dpkg-reconfigure locales For me the result was: Generating locales... en_AG.UTF-8... done en_AU.UTF-8... done en_BW.UTF-8... done en_CA.UTF-...


29

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.


28

Type the following in terminal to get rid of that error, sudo apt-get install language-pack-en-base sudo dpkg-reconfigure locales


28

Try the following commands sudo locale-gen fr_FR sudo update-locale LANG=fr_FR


26

The full list of key combinations is available on the local filesystem here: /usr/share/X11/locale/en_US.UTF-8/Compose Everything that starts with <Multi_key> is a Compose key combination. You'll find a lot of multi-number combinations producing stuff like: 34 as ¾ (10) as ⑩ And there are some fun (nearly easter egg) things in there too, ...


26

If you're troubleshooting, you'll likely post your results in some forum, or here, sooner or later. When that happens, it's much more simpler for other users to understand your logs and output, if they're not internationalised. That's to say, if you're using French or Chinese or Hindi or whatever as your system language, the output is likely to use terms ...


23

I would go another route, which is IMO better suited to the Ubuntu style. Use the packages provided. There are packages for each locale, and they do all the work for you... no need to edit /var files, which I always believed were not meant to be edited manually. sudo apt-get install language-pack-XX where XX stands for the language code. Installing a ...


23

export LC_ALL=C is enough. All subsequent command output will be in English. More information: What does "LC_ALL=C" do?


22

I've managed to get things running "normally" again. After trying lots of package re-installs etc, including fully removing IBus (all to no effect), I started to think that it may be caused by a config setting which re-installing doesn't modify. I had noticed that the output from locale was rather bereft, of UTF-8 assignments, so I checked this in a ...


22

Run the command locale - it should show your current locale. Generate the locales for french: sudo locale-gen fr_FR sudo locale-gen fr_FR.UTF-8 Also, try regenerating the supported locale list by running: sudo dpkg-reconfigure locales And update/change the current default locale: sudo update-locale LANG=fr_FR.UTF-8 Update Extra steps to try: ...


21

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.


20

This can happen sometimes on fresh minimal/alternate installs or in other situations. The fix is pretty simple. Try these, in the following order, testing after each to see if the situation is fixed: 1. Reconfigure locales sudo dpkg-reconfigure locales if that doesn't work, 2. Reinstall locale language-pack sudo apt-get --reinstall install language-...


19

You can list locales with localedef --list-archive or with locale -a Corresponding file size is given by ls -lh /usr/lib/locale/locale-archive To remove unused locales you can do sudo locale-gen --purge it_IT.UTF-8 en_US.UTF-8 && echo Success! where it_IT.UTF-8 and en_US.UTF-8 are the only two locales I want. The && echo "Success!"...


19

You can set locale manually using update-locale: sudo update-locale LANG=de_DE.UTF-8 LC_MESSAGES=POSIX Read the man page for more information. Alternatively, you can manually change your system's locale entries by modifying the file /etc/default/locale. For example on a German system, to prevent system messages from being translated, you may use: LANG=...


19

Fixed it by adding these lines to ~/.bash_profile on my local machine (OSX). export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8


19

I use this in my Dockerfile: # Set the locale RUN locale-gen en_US.UTF-8 ENV LANG en_US.UTF-8 ENV LANGUAGE en_US:en ENV LC_ALL en_US.UTF-8


17

Solution: Edit /etc/default/locale: LANG="en_US" LANGUAGE="en_US:en" Edit ~/.pam_environment: LANG=en_US Language=en_US Logout and Login or Reboot.


15

The best solution for me is to do this on a per-user basis in my own home directory. That way I don't have to edit a system-wide file. (Of course if you want this setting for all of the users on your system you are obviously forced to edit system files.) What I do is edit the file ~/.xsessionrc to contain the line "export LC_TIME=en_GB.utf8". That's it.



Only top voted, non community-wiki answers of a minimum length are eligible