Locales are broken in KDE5 konsole

bimon · 2021-01-16 09:25:19

Hello,

I use Trinity R14.0.9 and some KDE5 programs from the Devuan repository like for example konsole:

dpkg -al | grep konsole
ii  konsole                                                          4:16.12.0-4                                              amd64        X terminal emulator
ii  konsole-kpart                                                    4:16.12.0-4                                              amd64        Konsole plugin for Qt applications
ii  konsole-trinity                                                  4:14.0.9-0debian9.0.0+0                                  amd64        X terminal emulator for TDE
ii  konsolekalendar-trinity                                          4:14.0.9-0debian9.0.0+0                                  amd64        Trinity konsole personal organizer

After last upgrades of Trinity or may be Devuan backports I have got a strange behavior of locales in my system.

When I run command locale from konsole-trinity or lxterminal everything works fine:

locale
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

But if I run the same command locale from KDE konsole terminal I get a strange output like:

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

The actual problem why ask about this is I do not see national characters in mc ran from KDE konsole neither correct pseudo-graphics.
While everything works fine when ran from other non KDE terminals like konsole-trinity and lxterminal.

If running:

LANG=C mc

then at least pseudo-graphics is displayed correctly, but national symbols are not visible yet, displayed as ??????.

Last edited by bimon (2021-01-16 10:30:09)

Head_on_a_Stick · 2021-01-16 10:50:47

https://wiki.archlinux.org/index.php/KD … e_settings

bimon · 2021-01-16 11:01:48

Head_on_a_Stick wrote:

https://wiki.archlinux.org/index.php/KD … e_settings

Thanks for trying to help me, but I cannot find a plasma related locales config file:

find ~ -name plasma-localerc

find ~ -name \*locale\*

Head_on_a_Stick · 2021-01-16 11:08:54

bimon wrote:

I cannot find a plasma related locales config file

Try creating one yourself with the desired settings then (as suggested in the linked ArchWiki page).

Also check for ~/.config/plasma-locale-settings.sh, that can also change the locale configuration.

The Plasma utilities will expect their configuration to be managed by the Plasma configuration GUI so if you're using them elsewhere then some fiddling is to be expected.

bimon · 2021-01-16 11:30:06

I have created a file:

cat ~/.config/plasma-localerc
[Formats]
LANG=en_US.UTF-8

The problem is still there

But at least I know a direction where to search for a solution, it is somewhere a KDE personal locales config.

Last edited by bimon (2021-01-16 11:31:58)

Head_on_a_Stick · 2021-01-16 11:33:20

bimon wrote:

I have created a file:
[...]
The problem is still there

I'm not surprised — you've only specified a single element. Try adding all of the missing LC_whatever settings to the file.

bimon · 2021-01-16 11:41:06

Is it correct?

cat ~/.config/plasma-localerc
[Formats]
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

The problem is still there

bimon · 2021-01-16 11:50:34

Another problem appeared, even in other terminals locales became broken, I have already even removed ~/.config/plasma-localerc
and restarted Trinity:

locale
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
LANG=ru_RU.UTF-8
LANGUAGE=
LC_CTYPE=
LC_NUMERIC=
LC_TIME=
LC_COLLATE=
LC_MONETARY=
LC_MESSAGES=
LC_PAPER=
LC_NAME=
LC_ADDRESS=
LC_TELEPHONE=
LC_MEASUREMENT=
LC_IDENTIFICATION=
LC_ALL=

Two new problems:
1) locale: Cannot set LC_CTYPE to default locale: No such file or directory
2) Most fields became empty in non KDE terminals the same way as in KDE konsole

Something goes wrong

I even cannot revert back without rollback. Will try to see zfs diff.

Last edited by bimon (2021-01-16 11:52:42)

Head_on_a_Stick · 2021-01-16 12:41:08

bimon wrote:

Is it correct?

I'm not sure (I don't use Plasma or Qt in general) but I think LANGUAGE should be under [Translations] and I know you shouldn't be setting LC_ALL, just leave that one alone.

You could also try exporting the various locale settings via ~/.xsessionrc but that seems very hacky.

And perhaps your locales are mis-configured so try

# dpkg-reconfigure locales

bimon · 2021-01-16 12:59:15

Head_on_a_Stick wrote:

And perhaps your locales are mis-configured so try
# dpkg-reconfigure locales

Sure, I tried it several times earlier, it does not help at all, I even tried reinstalling different versions of this package and then reverted its version back.

I guess I have to leave the desktop environment and try to recover a good configuration of locales in a general text console at first at Alt+F1.

Last edited by bimon (2021-01-16 13:03:13)

bimon · 2021-01-16 13:39:00

After purging locales, installing this package once again and reconfiguring it for EN_US.UTF-8
I see several problems now:

1) In text terminal Alt+F1:
There are some fields still blank:

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="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=

Specifically LANGUAGE= and LC_ALL= are blank.

Also in text terminal I see a font which displays national symbols only partially while replacing about a half of them by a búbi character.
I guess I have to replace used font somehow?

2) During my last upgrade a few days ago I have replaced TDM display manager by nodm, and it seems nodm wipes out all localization fields.
Now I have replaced nodm by slim and at least I see in all terminals the same output of locales command which I see in text terminal described above in 1)

Btw, after replacing nodm by slim a few minutes ago I have correct working of all terminals in the desktop environment, all of them display mc and national symbols well. If I would not check specially I would not even notice that LANGUAGE= and LC_ALL= fields became blank.

Can you please let me know which script sets values for all LC_* fields from what I specified during re-configuring locales packages?
For now I would like to try at least to recover values for LANGUAGE= and LC_ALL= fields, how to do this?

Last edited by bimon (2021-01-16 13:43:06)

Head_on_a_Stick · 2021-01-16 15:36:32

bimon wrote:

There are some fields still blank

That is expected — LANGUAGE is a (GNU-specific) override and LC_ALL should *not* be set (as I have already explained).

I've just tried Debian's live KDE image and the locale output in konsole is exactly the same as the output you have posted from the TTY.

Edit /etc/default/locale if you have specific requirements or export the parameters from ~/.profile and source that file from ~/.xsessionrc to make sure it is read from any and all display managers.

See also https://wiki.debian.org/Locale

And I have to ask: is this from your box that has been dist-upgraded from the backports repository?

bimon · 2021-01-16 17:17:15

Head_on_a_Stick wrote:

And I have to ask: is this from your box that has been dist-upgraded from the backports repository?

Yes, it is after dist-upgrade -t=ascii-backports

Do you think nodm produces mentioned above problems only in a backported system like mine?

I am still not motivated for a downgrade anyway, just replaced nodm with slim, and almost everything is OK again.

People live and work on Ceres and it is fine for them generally.

As for me it is important to avoid significant configuration changes which is very seldom even with any and all backports installed on oldstable.

Though I still have to find a solution for text mode national symbols displayed incorrectly (only in Alt+F1..F6 terminal screens), I even did not pay attention to it earlier, may be before backports it was broken the same way.

Last edited by bimon (2021-01-16 17:26:05)

Head_on_a_Stick · 2021-01-16 19:10:45

bimon wrote:

Yes, it is after dist-upgrade -t=ascii-backports

Please be sure to mention this in any future support requests to prevent wasting the time of the people who chose to help you. Thanks.

bimon · 2021-01-16 19:33:06

I will mention my backported dist-upgrade status in my further requests. Thank you very much for your help.

We get answers here so quickly and they are very helpful and professional.

Does someone sponsor support work? I have seen many support replies during my life, and it sometimes takes much more time to get even an answer for expensive proprietary software issues those are much easier.

Last edited by bimon (2021-01-16 19:33:49)

Head_on_a_Stick · 2021-01-16 20:16:20

bimon wrote:

Does someone sponsor support work?

I sometimes get a doughnut from golinux, they know how grumpy I get when I'm hungry.

But seriously, thanks for your kind words :-)

bimon · 2021-01-16 21:42:52

I have corrected how symbols displayed in chvt 0 terminal by executing following command:

dpkg-reconfigure console-setup

and by selecting UTF-8 on the first page, and then my national specific option on the next page, and then Terminus (though others work too) font on the third page.

After that ls and mc displays correct characters in text terminal.

And IMHO oldstable Devuan ASCII upgraded to backports is very stable and nice :b

And Devuan is the best universal Linux distribution suitable for physical hosts.
I would run other distros only in its virtual machines.

Last edited by bimon (2021-01-16 21:48:38)

The officially official Devuan Forum!

#1 2021-01-16 09:25:19

Locales are broken in KDE5 konsole

#2 2021-01-16 10:50:47

Re: Locales are broken in KDE5 konsole

#3 2021-01-16 11:01:48

Re: Locales are broken in KDE5 konsole

#4 2021-01-16 11:08:54

Re: Locales are broken in KDE5 konsole

#5 2021-01-16 11:30:06

Re: Locales are broken in KDE5 konsole

#6 2021-01-16 11:33:20

Re: Locales are broken in KDE5 konsole

#7 2021-01-16 11:41:06

Re: Locales are broken in KDE5 konsole

#8 2021-01-16 11:50:34

Re: Locales are broken in KDE5 konsole

#9 2021-01-16 12:41:08

Re: Locales are broken in KDE5 konsole

#10 2021-01-16 12:59:15

Re: Locales are broken in KDE5 konsole

#11 2021-01-16 13:39:00

Re: Locales are broken in KDE5 konsole

#12 2021-01-16 15:36:32

Re: Locales are broken in KDE5 konsole

#13 2021-01-16 17:17:15

Re: Locales are broken in KDE5 konsole

#14 2021-01-16 19:10:45

Re: Locales are broken in KDE5 konsole

#15 2021-01-16 19:33:06

Re: Locales are broken in KDE5 konsole

#16 2021-01-16 20:16:20

Re: Locales are broken in KDE5 konsole

#17 2021-01-16 21:42:52

Re: Locales are broken in KDE5 konsole

Board footer