Ubuntu - Fontconfig warning: ignoring UTF-8: not a valid region tag

[hebbian]

I have this problem, I don't know it's OS warning or PhantomJS related issue. Any solution to this?

[danieljuhl]

I've had this issue too. It's not related to phantomjs, as far as I know. Please have a look at /etc/default/locale.

I added the following:

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

That resolved the issue for me.

[Xychun]

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

Solved it for me.

[wong2]

I'm facing the same issue, I've updated my /etc/default/locale as @danieljuhl suggested, but it doesn't work. I also tried @Xychun 's solution, still have the issue.

this is the output of locale command on my system:

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

[danieljuhl]

Remember to get a fresh terminal after the change.. have you done that, @wong2 ?

[woozyking]

I also get that not through command line but through running it using node.js (v5.5) child_process.execFile and this warning would be given through stderr stream despite being a warning. Before the child process execFile, there's another layer of express.js based API that accepts some parameters and a kue job framework to enqueue a job that eventually invokes the aforementioned execFile.

The weird thing is that if I invoke the execFile portion directly using command line, I wouldn't get this warning at all.

[DevAtCN]

I also faced same problem with DigitalOcean Ubuntu server. I fixed this using below commands:

sudo vim /etc/environment

Add below lines to the bottom of the "environment" file:

LANG="en_US.UTF-8"
LC_MESSAGES="C"
LC_ALL="en_US.UTF-8"

Now restart the OS and check locale and you will get:

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

Wola! You all set.

Hope this will help you.

Thanks.

[gopalkohli]

@danieljuhl solution works for me, Just reboot also the machine

[danieljuhl]

@forestallers or if connecting to a Remote machine through ssh, logout and login again (might also be enough locally

[safaorhan]

Still have this problem on Ubuntu 14.04.

Output of locale after reboot:

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

[sudarsanps]

I always get this same error , Fontconfig warning: ignoring UTF-8: not a valid region tag
i had installed UTF8 and when i list locale,I get the following
Note : My server is Ubuntu 16.04.1 and web server is nginx
LANG=C.UTF-8
LANGUAGE=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

I have tired all the other options listed above.still the result is same.How to solve this issue

[sudarsanps]

Hi, I have solved the above issue by doing the following:

sudo apt-get install language-pack-en-base
sudo dpkg-reconfigure locales
after this do:
sudo reboot

[stale]

Due to our very limited maintenance capacity, we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed (see #15395 for more details). In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!