Comment 7 for bug 1276072

OK, you're right, the problems came from this typo. Everything is fine, now (I did modified manually the ~/.pam_environment because the language selection at the session opening did not correct it once - I don't know why it works now).

I just insist on the fact that a write-protected ~/.pam_environment does not break anything: it is modified whatsoever (I will try it again, but I am quite confident on it).

And I still have to select the correct language at connection, it is not kept from one session to the next.