[SOLVED] Broken locales on KDE system

jensp · 2023-11-07 11:56:42

I have an issue where some applications have their locals set incorrectly when launching from Plasma. However when I start the same application from a Terminal (also started in Plasma) the locales are set correctly.

I suspect something around the environments being different, however I checked them in /proc and I can't find any significant differences. I tested with Filezilla which complains about unset LC_CTYPE when started from Plasma, it doesn't when I start from Terminal. I used xargs -0 -L1 -a /proc/$FILEZILLASPID/environ to check the env:

Output when started from Plasma:

LANG=en_US.UTF-8
LANGUAGE=en_US
LC_ADDRESS=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_NUMERIC=en_DE.UTF-8
LC_PAPER=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_TIME=de_DE.UTF-8

Output when started from Terminal:

LANG=en_US.UTF-8
LANGUAGE=en_US
LC_ADDRESS=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_PAPER=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_TIME=de_DE.UTF-8

Note that LC_CTYPE isn't set in either of them, but there are no issues with UTF-8 filenames when starting from Terminal. I have similar issues with other apps, for example Signal or Element, so it isn't specific to Filezilla.

Any other ideas what could be causing this issue?

Last edited by jensp (2023-11-07 12:03:01)

jensp · 2023-11-07 12:02:38

After removing the plasma-localrc settings it's working fine. No idea why I set them there and in the locale.conf setting anyway...

seth · 2023-11-07 14:30:16

You didn't necessarily: https://wiki.archlinux.org/title/KDE#Pl … e_settings

Arch Linux

#1 2023-11-07 11:56:42

[SOLVED] Broken locales on KDE system

#2 2023-11-07 12:02:38

Re: [SOLVED] Broken locales on KDE system

#3 2023-11-07 14:30:16

Re: [SOLVED] Broken locales on KDE system

Board footer