Closed
Description
Describe the bug:
XFCE VNC does not get fully localized into French (first image below) after installing the locale and setting the environment variables.
Expected behaviour:
The XFCE installed applications (using thunar as an example) to appear in French (second image below).
Steps to reproduce the issue:
In a docker file
FROM mltooling/ml-workspace-minimal:0.12.1
RUN \
apt-get update && \
apt-get install -y locales && \
sed -i -e 's/# fr_FR.UTF-8 UTF-8/fr_FR.UTF-8 UTF-8/' /etc/locale.gen && \
locale-gen && \
dpkg-reconfigure --frontend=noninteractive locales && \
clean-layer.sh
ENV LANG=fr_FR.UTF-8 LANGUAGE=fr_FR.UTF-8 LC_ALL=fr_FR.UTF-8
Build: sudo docker build -t mltest
Run: sudo docker run --rm -p 8080:8080 mltest
Navigate to desktop gui
Technical details:
- Workspace version: 0.12.1 (base)
- Docker versionL: 20.10.0
- Host Machine OS (Windows/Linux/Mac): Linux
- Command used to start the workspace :
sudo docker run --rm -p 8080:8080 mltest
- Browser (Chrome/Firefox/Safari): Firefox
Possible Fix:
I don't know :(
Additional context:
I've looked at and extended just an xfce specific image here and was able to get the UI to fully appear in French (see second image below). That image is based on ubuntu:16.04
.
Activity
raethlein commentedon Jan 14, 2021
Hey @Ito-Matsuda,
could you try out the following please:
Open a terminal in your running workspace
Execute the following commands to set the locale:
Restart vnc:
supervisorctl restart novnc vncserver
Refresh the noVNC page
Jose-Matsuda commentedon Jan 15, 2021
Hi there,


Unfortunately that doesn't seem to work.
then
I also get the
vncserver
failing / continuously exiting after running the restart vnc.raethlein commentedon Jan 18, 2021
Hm, I have not found any solution yet so maybe the problem is the version of Thunar? If that is the case, the problem might be solved as soon as it is updated.
Jose-Matsuda commentedon Jan 18, 2021
I think some
mo
files are not being generated correctly or there is something messing with it. If I get aThunar.mo
file from anubuntu:16.04
image from this other desktop projectand place it in either
/usr/share/locale/fr/LC_MESSAGES
or/usr/share/locale-langpack/fr/LC_MESSAGES
and it becomes localized.raethlein commentedon Jan 20, 2021
Hey @Ito-Matsuda, thanks for the hint with the
Thunar.mo
file!So, I have figured out that the translation files for Thunar are in the thunar-data package (e.g. here).
When I install the package in a ubuntu:16.04 docker container, then the
*.mo
files are copied to the/usr/share/locale/*
directory, while they are not copied in a ubuntu:18.04 or ubuntu:20.04 container.How to try out:
I guess you could just copy the translation file from the extracted directory. I have not found anything yet why the .mo files are not copied automatically when installing the package on ubuntu:18.04/20.04.
github-actions commentedon Apr 21, 2021
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 14 days
huapox commentedon May 16, 2021
My testing:
The xx.mo is generated when some app just installed.
locale-gen got
/usr/lib/locale/locale-archive
, but not xx.mo. xx.mo is in app's xx.deb package.The problem occured at the base-container, refrence src:
The keyConf:
/etc/dpkg/dpkg.cfg.d/docker
/etc/dpkg/dpkg.cfg.d/excludes
raethlein commentedon May 17, 2021
Great @huapox, thanks a lot for the answer! I just tested it and the entry in
/etc/dpkg/dpkg.cfg.d/excludes
is also the reason for the Ubuntu 18.04/20.04 images! If you comment the line out as you suggested and install the package again (e.g.dpkg -i thunar-data_1.6.15-0ubuntu1.18.04.1_all.deb
as described in the comment above), the translations are copied correctly! I think we are going to comment out that line in future versions of the workspace image by default then or at least add it to the FAQ section in the Readme