It seems that chromeRegistry.selectLocale() fails while profileManager is running. I tried to change UI language (ja-JP) and Content Locale (JP) on profileManager at creating new profile, UI language ja-JP could be applied but "JP" could not be set in user-locales.rdf. Check the user-locales.rdf under user profile, there is not "JP" entry. After profileManager is done, changing to "JP Region" by View -> Language and Web contents menu on Mozilla is working fine. After this operation, I can see "JP" region entries in user-locales.rdf.

Not sure it's right fix or not but how about using selectLocaleForProfile() instead of selectLocale() in createProfileWizard.js ??? It works on my environment. I'll attach the patch. Please evaluate.

Why is this an RDF bug?

I think chromeRegistry issue to go to tao or hyatt. Katakai san, since you have a patch, I assign this to you. The change is in profile manager, please ask for review to ccarlen or ben.

OK, I moved this to Profile Manager, changed summary, added Cc: ccarlen and ben. ccarlen or ben, can you review the patch? I'm thinking selectLocaleForProfile() should be used for createProfileWizard.js to install region (content locale).

I work on this as part of bug 80230. *** This bug has been marked as a duplicate of 80230 ***