Description Peter Åstrand 2016-11-09 13:24:25 CET

In some cases, the Windows client sends a localename of es_ES@modern. This causes tl-select-profile to crasch:

Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)
Traceback (most recent call last):
  File "/opt/thinlinc/libexec/tl-select-profile", line 298, in <module>
    locale . setlocale ( locale . LC_ALL , "" )
  File "/usr/lib64/python2.6/locale.py", line 513, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting
tl-xinit: client terminated and returned 0

The crash problem is bug 4512. However, I believe it is also incorrect for our client to send es_ES@modern in the first place. This is what our localename.c says:

    case LANG_SPANISH:
        switch (sub) {
        case SUBLANG_SPANISH:
            return "es_ES";
        case SUBLANG_SPANISH_MEXICAN:
            return "es_MX";
        case SUBLANG_SPANISH_MODERN:
            return "es_ES@modern";      /* not seen on Unix */

IOW, it seems to me that we should not send locale names which are not available on Linux.