keyboard-configuration set's console layout to us,af on update

Bug #698263 reported by Ralf Hildebrandt
100
This bug affects 17 people
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Fix Released
High
Colin Watson
Natty
Fix Released
High
Colin Watson

Bug Description

Binary package hint: console-setup

$ dpkg -l console-setup keyboard-configuration
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================-=====================-==========================================================
ii console-setup 1.57ubuntu2 console font and keymap setup program
ii keyboard-configuratio 1.57ubuntu2 system-wide keyboard preferences
hildeb@gilgamesch:~$ uname -a
Linux gilgamesch 2.6.37-12-generic #26-Ubuntu SMP Wed Jan 5 18:35:17 UTC 2011 x86_64 GNU/Linux
hildeb@gilgamesch:~$ lsb_release -rd
Description: Ubuntu natty (development branch)
Release: 11.04

WIth today's upgrade, the keyboard settings on the (framebuffer)-console are off. Although I'm specifying a german keyboard, I keep getting US keys (z and y swapped, no umlauts).

Tags: natty
Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

sudo apt-get install console-data

and selecting the proper keymap from "full list" worked wonders...

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Confirming because something odd is definitely going on here. In my case I'm seeing /etc/default/keyboard having:

XKBMODEL="a4techKB21"
XKBLAYOUT="us,af"
XKBVARIANT=","
XKBOPTIONS="grp_led:scroll"

(I've got UK/gb on both my machines but they both end up with this /etc/default/keyboard) and KDE seems to be matching this us/af choice.

Dave

Changed in console-setup (Ubuntu):
status: New → Confirmed
Philip Muškovac (yofel)
tags: added: natty
Philip Muškovac (yofel)
summary: - console keyboard mapping broken
+ keyboard-configuration set's console layout to us,af on update
Revision history for this message
Philip Muškovac (yofel) wrote :

Setting this high because this breaks again on every keyboard-configuration update and also changes the settings of the login screen, so you better not have characters in your username/PW that you can't input from an US keyboard.

Changed in console-setup (Ubuntu):
importance: Undecided → High
Revision history for this message
Colin Watson (cjwatson) wrote :

Mostly fixed, though I still need to deal with cleaning up systems broken by this bug (which I'll figure out before uploading).

Changed in console-setup (Ubuntu Natty):
status: Confirmed → Fix Committed
Colin Watson (cjwatson)
Changed in console-setup (Ubuntu Natty):
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package console-setup - 1.57ubuntu5

---------------
console-setup (1.57ubuntu5) natty; urgency=low

  * Drop misguided Ubuntu-specific code to migrate from console-setup/* to
    keyboard-configuration/* question names. This is already handled on
    upgrade by reading the old /etc/default/console-setup file
    (LP: #698263).
  * console-setup-udeb (<< 1.53) didn't set the seen flag in the installed
    system. Cope with this and avoid asking the layout and variant
    questions again if the default debconf priority is at least high
    (LP: #705883).
  * If we detect the above breakage (upgrading from anything between
    1.57ubuntu1 and 1.57ubuntu4 inclusive, and the XKB* values in
    /etc/default/keyboard differ from the commented-out values in
    /etc/default/console-setup), reset to the commented-out values in
    /etc/default/console-setup.
 -- Colin Watson <email address hidden> Fri, 28 Jan 2011 12:19:42 +0000

Changed in console-setup (Ubuntu Natty):
status: Fix Committed → Fix Released
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.