de_CH picked up as us

Bug #15142 reported by Tormod Volden
12
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

During installation, I chose Language->English, Location->Switzerland and
Keyboard->SwissGerman. However, when X11 has started, the american keyboard
layout is active. xorg.conf contains "us" instead of "de_CH".

Revision history for this message
Daniel Stone (daniels) wrote :

Could you please grab http://people.ubuntu.com/~daniels/detect-keyboard.sh, and run:
chmod +x detect-keyboard.sh
sudo $(pwd)/detect-keyboard.sh

Revision history for this message
Tormod Volden (tormodvolden) wrote :

aye-aye sir:

$ sudo $(pwd)/detect-keyboard.sh
layout is us
rules are xorg
model is pc104
options are
$

Revision history for this message
Daniel Stone (daniels) wrote :

Could you please add this to right underneath the DI_KEYMAP="$RET" line:
  echo "tuple is $DI_KEYMAP--$REALLANG"
and send me the output from that?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

tuple is sg-latin1--en_US

Revision history for this message
Philipp Schroeder (philipp.schroeder) wrote :

I can confirm this bug. I also chose Language->English, Location->Switzerland
and Keyboard->SwissGerman during installation.

But please note, I have slightly different findings on the console. They are:

$ sudo $(pwd)/detect-keyboard.sh
layout is gb
rules are xorg
model is pc104
options are

Strangely, the shellscript detects a English-british layout, even though
xorg.conf contains "us".

$ DI_KEYMAP="$RET"
$ echo "tuple is $DI_KEYMAP--$REALLANG"
tuple is --

BTW, tested on Breezy-preview.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Breezy: As of 2005-10-01, it seems like "ch" is the right layout, and not
"de_CH". I have been running dpkg-reconfigure xserver-xorg to see if it now gets
it right automatically, but then my old setting of de_CH is stuck somewhere even
if I answer Yes to the "the keyboard layout to be redetected" question.

The detect-keyboard.sh results are the same as in comment 2 and 4, except pc105
instead of pc104. pc105 is better, but in my case "presario" is probably the
best (Presario 700 laptop).

Revision history for this message
Philipp Schroeder (philipp.schroeder) wrote :

As of Breezy Release Candidate, I still have the problem reported originally.

Revision history for this message
Daniel Stone (daniels) wrote :

phillipp, could you please send the debug information from comments #1, #2, and #3?

Revision history for this message
Philipp Schroeder (philipp.schroeder) wrote :

Hi Daniel, here we go:

$ sudo ./detect-keyboard.sh
Password:
layout is us
rules are xorg
model is pc104
options are

$ DI_KEYMAP="$RET"
$ echo "tuple is $DI_KEYMAP--$REALLANG"
tuple is --

(on Breezy RC, fresh install, i386)

Revision history for this message
Tormod Volden (tormodvolden) wrote :

With Breezy RC, I get this, pretty much like before:

tuple is sg-latin1--en_US
layout is us
rules are xorg
model is pc104
options are

Philipp, you have to put that "tuple is" line inside the script.

Revision history for this message
Philipp Schroeder (philipp.schroeder) wrote :

Hey Tormod, thanks for pointing that out... I corrected the script now.

I get the same results:

tuple is sg-latin1--en_US
layout is us
rules are xorg
model is pc104
options are

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I can confirm that this has been fixed in Breezy final. Thanks a lot ! Greetings
from the country with the äöüàéè-keyboards :)

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Unfortunately, the problem is back in Dapper Drake Flight-2 !

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Running this in Dapper Flight-2:

$ sh detect-keyboard.sh
debconf: DbDriver "passwords" warning: could not open
/var/cache/debconf/passwords.dat: Permission denied
detect-keyboard.sh: line 11: debug_report_status: command not found
tuple is 10 debian-installer/keymap doesn't exist--en_US
layout is us
rules are xorg
model is pc104
options are

Revision history for this message
Daniel Stone (daniels) wrote :

tormod: you need to run it with sudo.

i have a rough idea of what I think has happened, but unfortunately our
illustrious installer dude is on holidays, so it probably won't get sorted 'till
the new year.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

It was the same output using "sudo", except for the passwords things.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Just for the record, this is working fine again in dapper flight 4.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.