Problems with locales


As many other Linux users, I'm often bugged by messages of missing LC and other locales on a clean install. To put it frank: I want to hit the guy responsible for this error message! Why not just choose some reasonable default?? Maybe I'm naive about this, so if you know why, please comment.

In case you want more info, someone put a better explanation here

This is how I fix it:
localedef -f UTF-8 -i en_US en_US.UTF-8
Here is an example of the annoying error message:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = "",
LC_MONETARY = "en_US.UTF-8",
LC_NUMERIC = "en_US.UTF-8",
LC_MESSAGES = "en_US.UTF-8",
LC_COLLATE = "en_US.UTF-8",
LC_CTYPE = "en_US.UTF-8",
LC_TIME = "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").
/usr/lib/postgresql/9.1/bin/psql: invalid option -- 'u'
Try "psql --help" for more information.

Comments

Post a Comment

Popular posts from this blog

Switching from Docker Desktop to Rancher Desktop on WSL2: Solving the Missing docker-credential-desktop.exe Error

Switching from Docker Desktop to Rancher Desktop on WSL2: Solving the Missing docker-credential-desktop.exe Error I’ve been happily running Kamal inside WSL2 on my home Windows desktop for a while. My original setup included an older Docker Desktop installation. Recently, I wanted to replicate this environment on a different machine, but I discovered that Docker Desktop had changed their licensing terms. Technically, I’m still covered by the new licensing terms, but I decided to try Rancher Desktop instead. Installing Rancher Desktop on WSL2 Installation was straightforward. I installed Rancher Desktop, configured it to integrate with WSL2, and disabled Kubernetes (since I don’t currently need it). My plan was to continue using the Docker CLI inside WSL2 alongside Rancher Desktop for container management. The Authentication Error However, when I was in WSL and tried to authenticate (for example, with Docker Hub via docker login), I ran into this error: ``` failed to store...
Read more

Running LXD/LXC on WSL2 with Ubuntu 20.04

Download Ubuntu 20.04 from the Microsoft Store sudo apt-get update sudo apt-get upgrade cd ~ git clone https://github.com/DamionGans/ubuntu-wsl2-systemd-script.git cd ubuntu-wsl2-systemd-script/ bash ubuntu-wsl2-systemd-script.sh sudo apt-get install snap (exit the shell and reopen it) Source: https://github.com/damionGans/ubuntu-wsl2-systemd-script To the IPv6 question I answer "none". $ sudo lxd init 2020/08/01 15:55:13 usbid: failed to load: open /usr/share/misc/usb.ids: no such file or directory Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (ceph, btrfs, dir, lvm) [default=btrfs]: Create a new BTRFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: Size in GB of the new loop device (1GB minimum) [default=50GB]: Would you like to connect to a MAAS server? (...
Read more

Proxmox Remote administration via VNC

Image
A few times I've needed to communicate via VNC, for instance when I was changing network configuration and couldn't use SSH or when I tried out Windows. Communicating with VNC to Proxmox wasn't so easy for me as it seemed in the documentation. Basically I never really got the " /etc/inetd.conf " thing to work, but this made it work from my local machine. This blog post is an alternative to the openbsd-inetd solution In the following: 2.2.2.2 is the IP of my Proxmox host 100 is the VM-ID you picked when you created the virtual machine ======================================================================== ssh -f -L 25901:127.0.0.1:5910 root@ 2.2.2.2 'nc -l -p 5910 -c "qm vncproxy 100 "'; "/Applications/TigerVNC Viewer 1.2.0.app/Contents/MacOS/TigerVNC Viewer" localhost:25901 ======================================================================== Please note that I only got TigerVNC to work, since all the other VNCs ha...
Read more