Caps Lock not working on TTYs/terminals

Feisty Herd 4 was released. Could you see if you still have issues with the newest release?

I'll put this as a casper bug for now since you were only able to test the live CD. Thank you for taking the time to file a bug report.

You indicate that the caps lock key isn't work in any of the ttys, does that mean it does not work either in the GUI or in a text console?

Hi

Tested Herd 4 and the problem is still there.

Caps Lock works fine in Gnome e.g. gedit, gnome-terminal. Problem only occurs on the terminals accessed using Ctrl+Alt+F*.

Problem persists in Herd 5 also.

Tested on the post beta snapshot 20070327 and it's still a problem there.

I note that the init script /etc/init.d/console-setup uses /bin/setupcon to setup the console keyboard mapping, which in turns uses the default values from /etc/defaults/console-setup (I think that's the correct filename) which specifies the US keyboard layout by default. This explains why I get US layout instead of GB so that's not an issue anymore.

However, I'm still not sure what's cause capslock to be ignored as the console-setup package's description implies it uses the same keyboard setup config as the X server, and under X the key works fine.

Have now upgrade to 7.04 on my main machine and can confirm this is still an issue. I don't think this is a Casper issue therefore I'm setting the package as console-setup as this is the component responsible for setting up the console text environment.

It's not working for me either. I'm using Feisty 7.04. Installed it on a P4 machine and two compaq laptops. I think this is a duplicate of this bug: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/63104

Hi shemgp

Thx for the suggestion but I don't think this is a dup of https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/63104 because in this case Caps Lock is not working at all, it hasn't been wrongly assigned as Shift Lock, and the LED is working fine.

Cheers

If you run 'sudo setupcon' from a console after boot, it'll work fine after that. I'm trying to work out why the initramfs setup that's supposed to set up the console doesn't seem to be taking, but not having any luck so far ...

This is not a duplicate of bug 63104 or those earlier Caps Lock bugs; it's a different issue.

console-setup (1.16ubuntu1) gutsy; urgency=low

  * Resynchronise with Debian. Remaining changes:
    - Use keymapper to generate decision trees for a restricted subset of
      the pc105 model.
    - If the detect-keyboard debconf plugin is available
      (cdebconf-newt-detect-keys in the installer), then offer to use it to
      detect the keyboard layout.
    - Only default to Canadian layout for fr_CA; use U.S. English for other
      *_CA locales.
    - Set default charmap for d-i to UTF-8.
    - Remove unhelpful defaults for several questions.
    - Allow preseeding of console-setup/modelcode, console-setup/layoutcode,
      console-setup/variantcode, console-setup/optionscode, and
      console-setup/fontsize.
    - Reset console-setup/toggle to the default if it's set to "No toggling"
      and you select a non-Latin layout.
    - Change the default font from Terminus to VGA where supported.
    - Add a few bits of installer integration to console-setup-udeb borrowed
      from kbd-chooser.
    - console-setup Depends: perl; something in ckbcomp is causing perl to
      'use utf8' implicitly, and some of the necessary modules aren't in
      perl-base.
    - Run kbd_mode on each tty in ACTIVE_CONSOLES rather than on the current
      tty, since the current tty might belong to X and changing X's tty out
      of raw mode is a very bad idea.
    - Automatically save the font and keymap to /etc in
      /etc/init.d/console-setup if it isn't being run from init. Similarly,
      ensure that the font and keymap are saved to /etc during initial
      installation.
    - Disable workaround in ckbcomp for the kernel not applying Caps Lock to
      non-ASCII letters, except for Turkish layouts; the cure is worse than
      the disease because it makes Caps Lock equivalent to Shift Lock.
    - Use 'setupcon --save-only' to make sure the font is available on the
      root filesystem for the next boot but not to load it immediately,
      avoiding console manipulation when X or usplash is running.
    - Set keymap and font in the initramfs if possible.
    - Set default variant for French to oss.
    - Fix handling of commas in layout and variant names.
    - Fix keymap reduction not to try to express keymap A in terms of keymap
      B when B includes keys not mapped by A.
    - debian/config.proto: Set sparc default model to pc105.
    - debian/control: Remove outdated note about loadkeys in
      console-setup-udeb's description.
  * Allow kbd's initramfs hook as an alternative to that provided by
    console-tools.
  * Don't run 'setupcon -k' from rcS if usplash is running, as that means
    the console will be in raw mode and loadkeys will do confusing things to
    the keymap (LP: #84156).

console-setup (1.16) unstable; urgency=low

  * Update ckbconf with the most recent list of xkeysyms.
  * Thanks to Colin Watson and Ubuntu team for the many bugs and
    improvements fixed in this release. Patches were provided by Colin
    Watson:
    - Do not sorce the debconf library in the middle of the postinst,
      closes: #420831.
    - Remove from the source package several directories
      debian/UDEB-PACKAGE-NAME. (The udebs were remove...

It turns out that we didn't quite fix this after all, and it's still broken in 8.10 (probably 8.04 as well). I have a fix, but am reopening this bug to serve as a duplicate sink.

Actually, on further inspection this bug was quite specific to keyboard mapping, and so isn't appropriate for the current problem, so I'm closing this again. Sorry for the noise!