us misdetected as jp

Bug #74375 reported by Colin Watson
22
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Fix Released
High
Colin Watson

Bug Description

In console-setup-pc-ekmap 1.13ubuntu3, the generated /usr/share/console-setup-mini/pc105.tree incorrectly causes a us keyboard to be misdetected as jp. The relevant chunk is as follows:

STEP 62
FINDP ¿
YES 64
NO 63
STEP 63
MAP jp
STEP 64
FINDP ¨
YES 69
NO 65
STEP 65
FINDP ł
YES 29
NO 66
STEP 66
FINDP š
YES 68
NO 67
STEP 67
MAP us

However, us has no ¿ key, so it should be on the NO path from step 62, not the YES path.

Colin Watson (cjwatson)
Changed in keymapper:
importance: Undecided → High
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This turns out not to be a keymapper bug at all (whoops); the input it's being given by console-setup is incorrect.

Revision history for this message
Colin Watson (cjwatson) wrote :

console-setup (1.13ubuntu9) feisty; urgency=low

  * Keyboard/kbdcompiler: Fix keymap reduction not to try to express keymap
    A in terms of keymap B when B includes keys not mapped by A, fixing a
    number of incorrectly-reduced keymaps (LP: #74375).
  * Keyboard/kbdcompiler: Update handling of jp to match
    debian/config.proto.
  * Keyboard/keymaptree.use: Remove jp; we cannot detect it correctly
    without further intelligence, as it's designed for jp106 keyboard
    models.

 -- Colin Watson <email address hidden> Sat, 17 Mar 2007 10:06:05 +0000

Changed in console-setup:
assignee: nobody → kamion
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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