Installer does not add proper locale to locale.gen, GNOME settings can't see any language
Closed, ResolvedPublic

Description

What happens:

Installed using latest live PureOS ISO, but users report this for OEM ISO as well.

GNOME settings cannot see any language or formats:

Workaround

After I did:

sudo sh -c 'echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen'
sudo sh -c 'echo "bs_BA.UTF-8 UTF-8" >> /etc/locale.gen'
sudo sh -c 'echo "sr_RS UTF-8" >> /etc/locale.gen'
sudo sh -c 'echo "sr_RS@latin UTF-8" >> /etc/locale.gen'
sudo locale-gen

I was able to select English, Bosnian or Serbian language and/or formats:

What should happen:

The installer should pick this up automatically.
GNOME settings should be able to select any language, regardless of what's un-commented in locale.gen.

mladen.pejakovic changed the edit policy from "Custom Policy" to "Restricted Project (Project)".
mak added a subscriber: mak.Aug 10 2018, 1:15 AM

Did you consider reporting this issue to GNOME as well?

mak claimed this task.Aug 13 2018, 2:49 PM

@mladen.pejakovic

The installer should pick this up automatically.

This might be fixed. The other issue I haven't looked into yet, but it originates from GNOME assuming Fedora behavior which just doesn't apply to Debian.
Not sure how to deal with that, but when the installer issues are dealt with I will look into that next.
Can you please test if this issue is fixed in my test image from http://downloads.puri.sm/playground/2018-08-10/ ?
Please be aware that the playground image suffers from unrelated issue T542

These are actually two issues, I realize this now, sorry.

First one: installer does add appropriate locale to locale.gen. This one is fixed in live ISO 20180721 image. Will test the playground OEM as well.
Second: GNOME settings cannot select any other language than what is enabled in locale.gen. Not fixed!

The second issue is important IMHO: PureOS should be easy-to-use system, and users should be able to select whatever language they want without needing to tinker with locale.gen file.

mak closed this task as "Resolved".

@mladen.pejakovic I've split this issue and created T549 so we can track the GNOME bug individually.
Thanks for the feedback!

Add Comment