Comment 3 for bug 2012552

The latter comment reminds me of bug #2011313, where the underlying issue was a failure (for some reason) to fetch user data. One side effect in that case was that it resulted in a language variable having a NULL value, and then it failed when trying to convert it to a valid locale name.

Anyway, the wording "is not a valid locale name" comes probably from the user_locale_validate() function in accountsservice (0010-set-language.patch).

And "Couldn't set FormatsLocale" comes from the set_formats_locale() function in g-c-c (Adapts-the-region-capplet-and-the-language-chooser-in-the.patch).