Tmux locale problem
-
Hello
Running the pfSense 2.4.0 snapshots based on FreeBSD 11. I like to have bash and tmux installed on the firewall for running persistent processes in the background. Under pfSense 2.3 it worked but under 2.4 I get the error "tmux: invalid LC_ALL, LC_CTYPE or LANG".
When running "declare -x LC_ALL=en_US.UTF-8" I get "bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory"
How do I fix this (as I think it is related to the problem)
Thanks
-
comment out the SendEnv LANG LC_* line in the local /etc/ssh/ssh_config file.
-
Nope, didn't work.
(Running OS X 10.11)
I don't have this problem with any of my Linux servers or had it with pfSense 2.3 so I assume it's a problem with pfSense 2.4 BETA and locales at the servers end.
-
When running "declare -x LC_ALL=en_US.UTF-8"
So stop running it when it doesn't work? SIGDUH! :P
Extra hint:
ls -la /usr/share/locale/en_US.UTF-8/
-
Directory is empty :/
My current theory is that the locales got corrupted when I upgraded from 2.3 to 2.4 beta in November 2016 (when this problem started)
[root@router ~]# ls -la /usr/share/locale/en_US.UTF-8/ total 12 drwxr-xr-x 2 root wheel 512 Jan 27 17:43 . drwxr-xr-x 209 root wheel 5120 Jan 22 21:50 ..
-
Decided to reinstall pfSense for other reasons. Above directory is empty as always. Still having the same problem, but with locales not set in login.conf as I tried before.
[root@router ~]# tmux tmux: need UTF-8 locale (LC_CTYPE) but have US-ASCII [root@router ~]# locale LANG= LC_CTYPE="C" LC_COLLATE="C" LC_TIME="C" LC_NUMERIC="C" LC_MONETARY="C" LC_MESSAGES="C" LC_ALL=
Thanks
-
I must be speaking Chinese I guess…
When running "declare -x LC_ALL=en_US.UTF-8"
So do NOT run that.
-
Oh you're funny.
What part of I'm not running it repeatedly don't you understand?
It was just once to sure if it would fix the problem.
As in. I'm completely stock in terms of locales, a fresh install of pfSense, no funny login.conf or bashrc things and yet running tmux I get the above error mentioned.
Next question
-
It wouldn't fix a problem, plus UTF-8 on console is not exactly something that'd be working out of the box on FreeBSD. https://wiki.freebsd.org/Newcons
-
It wouldn't fix a problem, plus UTF-8 on console is not exactly something that'd be working out of the box on FreeBSD. https://wiki.freebsd.org/Newcons
tmux worked on FreeBSD 10. Ah well, thanks anyways.
-
Sorry for bumping
Just thought I'd mention that GNU screen works fine with 2.3.4