Univention Bugzilla – Bug 30129
Locals aren't evaluated
Last modified: 2014-06-12 09:19:45 CEST
The default locals aren't necessary committed when installing to a client, resulting in an ambiguous non utf-8 compatible state. Setting locale/default via ucr or registry solves the problem. It could both be reproduced using a custom as well as the thin client image.
Please provide more details. Which locale was set on the UCS server serving the UCC images? The locale from the UCS server is set as default on the UCC clients. How did you install the client? PXE boot or local installation?
The Server has de_DE.UTF-8 the clients default with ucr get is also set to de_DE.UTF-8. The Problem was that the files were not comitted. ucr commit also solved the issue. The Systems were rolled out using PXE and both MS2 and MS3 of the integration package.
I can confirm that, without UCR policies the default locale is empty and the german locale of the server is not applied.
UCC 2.0 client, no policies, just "locale=de_DE.UTF-8:UTF-8" in the clients pxe config, after the rollout the locale seems to be fine -> ucr get locale/default de_DE.UTF-8:UTF-8 -> more /etc/locale.gen de_DE.UTF-8 UTF-8 -> root@ucc1:~# ls -la /sad ls: Zugriff auf /sad nicht möglich: Datei oder Verzeichnis nicht gefunden
Verified, i could not reproduce the issue.
UCC 2.0 has been released: http://docs.univention.de/release-notes-ucc-2.0.html If this error occurs again, please use "Clone This Bug".