Pressing Caps Lock toggles LED even when mapped to another key

[Seth Forshee]

I have the the Caps Lock and Esc keys swapped; that is, pressing Caps Lock generates an Esc keycode and vice versa. This was done using the options in the keyboard settings, which seem to have disappeared recently.

With this setup, pressing either the Esc and Caps Lock keys will toggle the Caps Lock LED. As a result the LED does not accurately reflect the state of the caps lock function. My expectation is that only the key which toggles the caps lock function (in this case Esc) should toggle the LED, and that the state of the LED should always accurately reflect the state of the caps lock function.

----------
For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322.
----------

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity-system-compositor 0.0.1+13.10.20130903-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Thu Sep 5 14:04:28 2013
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00eb]
InstallationDate: Installed on 2012-10-24 (316 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
LightDMLog: Error: [Errno 13] Permission denied: '/var/log/lightdm/lightdm.log'
MarkForUpload: True
SourcePackage: unity-system-compositor
UnitySystemCompositorLog: Error: [Errno 13] Permission denied: '/var/log/lightdm/unity-system-compositor.log'
UpgradeStatus: Upgraded to saucy on 2013-05-01 (127 days ago)
version.libdrm: libdrm2 2.4.46-1
version.lightdm: lightdm 1.7.12-0ubuntu1
version.mesa: libegl1-mesa-dev N/A

[Timo Aaltonen (tjaalton)]

guess it's hardwired somewhere lower in the stack

[Seth Forshee (sforshee)]

Well, all I can say is that with the old graphics stack the LED always reflected the actual state of the caps lock function, i.e. it did not have this problem.

[Norbert (nrbrtx)]

What do you have in /etc/default/keyboard, Seth?

[Seth Forshee (sforshee)]

Norbert: see below. Also I should add that I switched this machine back to the non-xmir stack and the LED behaves as expected. Switching back to xmir (i.e. uncommenting "type=unity" in /etc/lightdm/lightdm.conf.d/10-unity-system-compositor.conf) still exhibits the issue.

$ cat /etc/default/keyboard
# Check /usr/share/doc/keyboard-configuration/README.Debian for
# documentation on what to do after having modified this file.

# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.

XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS=""

# If you don't want to use the XKB layout on the console, you can
# specify an alternative keymap. Make sure it will be accessible
# before /usr is mounted.
# KMAP=/etc/console-setup/defkeymap.kmap.gz

[Norbert (nrbrtx)]

Thank you, Seth.
It seems that the problem is connected with xmir/non-xmir stack.
Let's wait for a patch :)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.