| 2012-01-23 18:55:16 |
Ben Howard |
bug |
|
|
added bug |
| 2012-01-23 18:55:28 |
Ben Howard |
ubuntu: assignee |
|
Ben Howard (utlemming) |
|
| 2012-01-23 18:55:32 |
Ben Howard |
ubuntu: importance |
Undecided |
High |
|
| 2012-01-23 19:34:32 |
Ben Howard |
description |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric.
ubuntu@ip-10-101-11-188:~$ locale -a
C
C.UTF-8
en_US.utf8
POSIX
With the default SSH configuration (both as a client and the cloud-image SSH server), any non-en_US.UTF-8 locale will be passed through to the cloud-image. The result is that
For Oneiric, the cloud images force "en_US.UTF-8" for the locale. |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default. Users who SSH in with a $LANG of something else is ignored.
Currently the way to set the lang is to use cloud-config. |
|
| 2012-01-23 19:34:50 |
Ben Howard |
ubuntu: importance |
High |
Low |
|
| 2012-01-23 20:19:42 |
Ubuntu Foundations Team Bug Bot |
tags |
|
bot-comment |
|
| 2012-01-23 23:53:32 |
Ben Howard |
description |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default. Users who SSH in with a $LANG of something else is ignored.
Currently the way to set the lang is to use cloud-config. |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default unless a user sets the locale via cloud-config in cloud-init. Users who SSH into a cloud-image with LANG="<SOMETHING ELSE>" will have an invalid LANG seting.
IMHO, this is a poor user experience for international users. We either need to turn off "Accept LC_*" in /etc/sshd/config, installed (and thus bloat the images) all the language packs or come up with a way to dynamically install the the languages.
Example:
LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Warning: Permanently added 'ec2-23-20-37-252.compute-1.amazonaws.com' (ECDSA) to the list of known hosts.
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_GB.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE=en_US.UTF-8
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
ubuntu@domU-12-31-39-16-C8-46:/home/ubuntu$ locale -a
C
C.UTF-8
en_US.utf8
POSIX |
|
| 2012-01-24 00:18:19 |
Ben Howard |
summary |
cloud-images don't understand other locales in precise |
cloud-images don't accept LANG settings |
|
| 2012-01-24 00:23:00 |
Ben Howard |
description |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default unless a user sets the locale via cloud-config in cloud-init. Users who SSH into a cloud-image with LANG="<SOMETHING ELSE>" will have an invalid LANG seting.
IMHO, this is a poor user experience for international users. We either need to turn off "Accept LC_*" in /etc/sshd/config, installed (and thus bloat the images) all the language packs or come up with a way to dynamically install the the languages.
Example:
LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Warning: Permanently added 'ec2-23-20-37-252.compute-1.amazonaws.com' (ECDSA) to the list of known hosts.
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_GB.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE=en_US.UTF-8
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
ubuntu@domU-12-31-39-16-C8-46:/home/ubuntu$ locale -a
C
C.UTF-8
en_US.utf8
POSIX |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default unless a user sets the locale via cloud-config in cloud-init. Users who SSH into a cloud-image with LANG="<SOMETHING ELSE>" will have the LANG setting ignored. On Precise if the LANG is invalid, then the environment will reflect the invalid language; if the LANG is valid, then it will be ignored.
IMHO, this is a poor user experience for international users. We either need to turn off "Accept LC_*" in /etc/sshd/config, install (and thus bloat the images) all the language packs or come up with a way to dynamically install the the languages.
Example:
LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Warning: Permanently added 'ec2-23-20-37-252.compute-1.amazonaws.com' (ECDSA) to the list of known hosts.
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=en_US.UTF-8
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
ubuntu@domU-12-31-39-16-C8-46:/home/ubuntu$ locale -a
C
C.UTF-8
en_US.utf8
POSIX
----
Invalid LANG setting -- the following example is SSH'ing with an invalid LANG="?". Notice that the LANG is reflected in the environment. In this case /etc/default/locale has 'LANG="en_US.UTF-8"' set.
ben@padfoot:~/Desktop$ LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_GB.UTF-8
...
ubuntu@domU-12-31-39-16-C8-46:~$ sudo locale-gen en_GB.UTF-8
Generating locales...
en_GB.UTF-8... done
Generation complete.
ubuntu@domU-12-31-39-16-C8-46:~$ exit
ben@padfoot:~/Desktop$ LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
LANG=en_US.UTF-8
.. |
|
| 2012-03-15 22:45:05 |
Ben Howard |
ubuntu: importance |
Low |
Critical |
|
| 2012-03-15 22:45:08 |
Ben Howard |
ubuntu: status |
New |
Confirmed |
|
| 2012-03-30 18:08:05 |
Scott Moser |
description |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default unless a user sets the locale via cloud-config in cloud-init. Users who SSH into a cloud-image with LANG="<SOMETHING ELSE>" will have the LANG setting ignored. On Precise if the LANG is invalid, then the environment will reflect the invalid language; if the LANG is valid, then it will be ignored.
IMHO, this is a poor user experience for international users. We either need to turn off "Accept LC_*" in /etc/sshd/config, install (and thus bloat the images) all the language packs or come up with a way to dynamically install the the languages.
Example:
LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Warning: Permanently added 'ec2-23-20-37-252.compute-1.amazonaws.com' (ECDSA) to the list of known hosts.
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=en_US.UTF-8
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
ubuntu@domU-12-31-39-16-C8-46:/home/ubuntu$ locale -a
C
C.UTF-8
en_US.utf8
POSIX
----
Invalid LANG setting -- the following example is SSH'ing with an invalid LANG="?". Notice that the LANG is reflected in the environment. In this case /etc/default/locale has 'LANG="en_US.UTF-8"' set.
ben@padfoot:~/Desktop$ LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_GB.UTF-8
...
ubuntu@domU-12-31-39-16-C8-46:~$ sudo locale-gen en_GB.UTF-8
Generating locales...
en_GB.UTF-8... done
Generation complete.
ubuntu@domU-12-31-39-16-C8-46:~$ exit
ben@padfoot:~/Desktop$ LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
LANG=en_US.UTF-8
.. |
The cloud images currently only support "en_US.UTF-8" locales in Oneiric and Precise by default unless a user sets the locale via cloud-config in cloud-init. Users who SSH into a cloud-image with LANG="<SOMETHING ELSE>" will have the LANG setting ignored. On Precise if the LANG is invalid, then the environment will reflect the invalid language; if the LANG is valid, then it will be ignored.
IMHO, this is a poor user experience for international users. We either need to turn off "Accept LC_*" in /etc/sshd/config, install (and thus bloat the images) all the language packs or come up with a way to dynamically install the the languages.
Example:
LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Warning: Permanently added 'ec2-23-20-37-252.compute-1.amazonaws.com' (ECDSA) to the list of known hosts.
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=en_US.UTF-8
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
ubuntu@domU-12-31-39-16-C8-46:/home/ubuntu$ locale -a
C
C.UTF-8
en_US.utf8
POSIX
----
Invalid LANG setting -- the following example is SSH'ing with an invalid LANG="?". Notice that the LANG is reflected in the environment. In this case /etc/default/locale has 'LANG="en_US.UTF-8"' set.
ben@padfoot:~/Desktop$ LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_GB.UTF-8
...
ubuntu@domU-12-31-39-16-C8-46:~$ sudo locale-gen en_GB.UTF-8
Generating locales...
en_GB.UTF-8... done
Generation complete.
ubuntu@domU-12-31-39-16-C8-46:~$ exit
ben@padfoot:~/Desktop$ LANG="en_GB.UTF-8" ssh ec2-23-20-37-252.compute-1.amazonaws.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-10-virtual i686)
ubuntu@domU-12-31-39-16-C8-46:~$ locale
LANG=en_US.UTF-8
..
Related Bugs:
* bug 859814: Locale issues with beta-1/2 cloud-images |
|
| 2012-03-30 18:08:11 |
Scott Moser |
bug |
|
|
added subscriber Scott Moser |
| 2012-12-03 19:13:07 |
Ben Howard |
ubuntu: status |
Confirmed |
Won't Fix |
|
