uses cached keymap even when reading a user configuration file

[MDill]

I am running Ubuntu 8.10 with console-setup ver 1.25ubuntu4

Setting XKBLAYOUT="us" and XKBVARIANT="dvorak" in "$HOME/.console-setup" and running "sudo /bin/setupcon" fails to load the dvorak keymap. The "/etc/console-setup/boottime.kmap.gz mapping is always loaded instead.

In line 307 of /bin/setupcon the variable VARIANT is checked when I believe XKBVARIANT ought to be. This causes all the XKB... options to be ignored if one is using a normal "$HOME/.console-setup" configuration rather than a "$HOME/.console-setup.VARIANT" configuration. The VARIANT variable should only be evaluated early in the script to load the proper configuration file.

[Colin Watson (cjwatson)]

No, VARIANT is correct there - it means the configuration file variant rather than the keyboard variant. The problem is that we're using the cached file even when CONFIG=$USER_CONFIG. I'll get this fixed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package console-setup - 1.28ubuntu6

---------------
console-setup (1.28ubuntu6) jaunty; urgency=low

  * Don't escape '(' and ')' when decoding/encoding the codeset, as the
    pattern is passed to grep and this causes parentheses to be interpreted
    as regular expression groups (thanks to Dmitry Agafonov for pointing out
    the problem).
  * If reading a user configuration file, disable --save, and don't use
    /etc/console-setup/boottime.kmap.gz (LP: #332728).
  * Update Keyboard/KeyboardNames.pl based on xkb-data 1.5-2ubuntu5.

 -- Colin Watson <email address hidden> Mon, 02 Mar 2009 16:30:50 +0000