[Pkg-kbd-devel] Bug#354564: console-setup: Function keys F10-F12 don't work

[Balogh, Bálint]

Package: console-setup
Version: 1.5
Severity: important


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3-grsec
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages console-setup depends on:
ii  console-terminus              4.16-3
ii  debconf [debconf-2.0]         1.4.70

Versions of packages console-setup recommends:
ii  console-tools              1:0.2.3dbs-60

-- debconf information:
* console-setup/variant: U.S. English
  console-setup/modelcode: pc101
  console-setup/fontsize: 16
  console-setup/layoutcode: us
  console-setup/dont_ask_layout:
* console-setup/altgr: No AltGr key
* console-setup/ttys: /dev/tty[1-6]
* console-setup/codeset: Lat15
  console-setup/toggle: No toggling
* console-setup/fontface: Terminus
* console-setup/fontsize-text: 16
* console-setup/compose: No compose key
  console-setup/switch: No temporary switch
* console-setup/charmap: ISO-8859-1
  console-setup/optionscode:
* console-setup/layout: U.S. English
  console-setup/variantcode:
* console-setup/model: Generic 101-key PC
* console-setup/fontsize-fb: 1
--

The function keys F10-F12 don't work on the console after installing
console-setup. Looking at /etc/console-setup/boottime.kmap.gz revealed
that ckbcomp doesn't recognize key symbols F10, F11, F12. Relevant
excerpt from boottime.kmap.gz:
keycode 68 = VoidSymbol VoidSymbol [...]

Manually running the command "ckbcomp -model pc101 us" yields the
following:
keycode 68 = U+0f10 U+0f10 [...]

It seems that ckbcomp falsely interprets the symbols F10, F11, F12 as
unicode characters in hexadecimal form.