I think entering that export command will only affect that terminal and things “spawned” from it. You’ll probably have to find where Cryptomator is picking its settings up from. You might check the /etc/locale.conf and /etc/environment files. Unfortunately, there are a lot of places where that variable might be incorrectly set. Places like the systemd service file that starts the application and your ~/.bash{_profile,rc} files are also possibilities. I think if you use the locale command, you might be able to see a more complete listing of the various LANG variables.
@ilikelinux I didnt change fonts at all I think? But I see fonts appearing, weird. The standard fonts I use are the same. but see the output below maybe
@vekruse Ok I printed that to a file, anything I should look for? I searched for “code”:
interesting finds:
-rw-r--r--. 1 root root 269 12. Feb 21:03 /etc/anthy-unicode.conf
lrwxrwxrwx. 1 root root 62 12. Feb 21:03 /etc/fonts/conf.d/61-adobe-source-code-pro.conf -> /usr/share/fontconfig/conf.avail/61-adobe-source-code-pro.conf
-rw-r--r--. 1 root root 86 12. Feb 21:03 /etc/xdg/accept-languages.codes
I got more errors, here is a LUKS dialog requesting the sudo password (working normally)
You should be looking for “LC_”. At the time the problem started, something must have been changed. Usually that would be a file somewhere in /etc that has been created or modified recently.
I can imagine that the above file interferes with the default config /etc/user-dir.conf:
# This controls the behaviour of xdg-user-dirs-update which is run on user login
# You can also have per-user config in ~/.config/user-dirs.conf, or specify
# the XDG_CONFIG_HOME and/or XDG_CONFIG_DIRS to override this
#
enabled=True
# This sets the filename encoding to use. You can specify an explicit
# encoding, or "locale" which means the encoding of the users locale
# will be used
filename_encoding=UTF-8