Bug 39138 - System setup uses locale from selected location instead of configured language
System setup uses locale from selected location instead of configured language
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
Depends on:
Blocks: 39635
  Show dependency treegraph
 
Reported: 2015-08-10 19:02 CEST by Erik Damrose
Modified: 2019-01-03 07:15 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2015-08-10 19:02:08 CEST
First step in appliance mode is to set a Language and location. However, if e.g. german is selected as language and a location with an english locale (New York) is selected, the system is configured with en_US as locale/default. In this example, the welcome screen is then shown in english, after the setup has been in german.

The default locale should be set according to the language selection, not the location
Comment 1 Florian Best univentionstaff 2015-11-23 15:36:45 CET
This is because system setup should run with the selected keyboard layout.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:15:54 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.