does not offer C.UTF-8 locale

[Piotr Engelking]

In Debian, LightDM does not offer C.UTF-8 locale during login, see:

    https://bugs.debian.org/844991

The code includes a function to filter UTF-8 locales, but it is not always
used. The attached patch against trunk fixes the problem.

[Robert Ancell (robert-ancell)]

Is it useful to show the C locale (it's not really a language)?

Are there other languages that might have the .UTF-8 suffix?

[Piotr Engelking (inkerman42)]

If it wasn't useful for me I wouldn't file the bug.

A large number of locales in Debian have the .UTF-8 suffix but other than C.UTF-8 (and perhaps some of the user-created custom locales, but this is would be extremely rare) they are not shown by locale -a, so LightDM uses names ending in .utf8 instead.

[Robert Ancell (robert-ancell)]

Can you explain how the C locale is useful to be shown? I'm wondering if with this change we should filter it out.

[Preston Baker (presbaker)]

I'm here for nearly the same problem that I got when using musl C library and musl locales https://github.com/rilian-la-te/musl-locales which uses uppercase ".UTF-8" suffixes for the locale names. Despite my very special use case I'm shure we should be generally case independent on locale suffixes. Also, since I was up to propose a patch similar to the one given, I would like to see it applied as well.

Wether it was useful to filter out the "C" local should depend on the use case Piotr is going to point out.

Thanks for your work!

[Piotr Engelking (inkerman42)]

C.UTF-8 is a useful fallback when other available locales are unsuitable for user.

Also, currently C.UTF-8 is not offered even if it is configured as the default system locale.

[Raphaël Hertzog (hertzog)]

Furthermore, when C.UTF-8 is the default locale and the user does nothing, he ends up with the first locale in the list... which is aa_DJ.utf8 on Kali images that have locales-all installed. Not very helpful either.

[Raphaël Hertzog (hertzog)]

For reference, this "unexpected locale" problem has been reported to Kali here and has been the basis for my last comment: https://bugs.kali.org/view.php?id=4254

Let me know if you prefer to handle this as a separate issue and I'll file a new ticket.