Ubuntu
console-setup package

caps lock led doesn't work on the virtual terminals

Bug #63104 reported by Edmundo
8
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

If I activate/deactivate caps lock, the led doesn't turn on or off. It is always off.. though the intended effect actually works.

On X caps lock works normally.

I'm using kubuntu edgy updated yesterday from dapper.

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

this would be due to kmilo having not been started, which deals with all those special keys, i expect. or a part of X.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Same problem here on Ubuntu Edgy Beta, in a VT caps lock can be activated but the Caps LED doesn't show this. Pressing Alt+F7 to switch to X when CAPS lock is activated doesn't work, which is very annoying.

Revision history for this message
Nick Booker (nmbooker) wrote :

Same here with Edgy Final (updated via Web from Beta).
After a bit of detective work, I've found that the LED stops responding when the /etc/init.d/keyboard-setup script runs as part of rcS.d. The package which owns this script is console-setup, and the script it calls is /bin/setupcon which is owned by the same package (console-setup). If I disable /etc/init.d/keyboard-setup the LED stops responding later in the boot process when /etc/init.d/console-setup is run.

NEW INFO: Caps seems to be acting as a Shift Lock (Sticky Shift), not Caps Lock - I'm getting : rather than ;, @ rather than ' etc (British keyboard). Maybe Pascal De Vuyst, eantoranz or some other victim could verify this if they're still struggling (and if not, please share how you fixed it!). If the Caps key isn't even working as Caps Lock, then maybe this explains the LED not functioning correctly.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Caps Lock key is indeed handled as Shift Lock, as indicated by the following command:
$ dumpkeys | grep 58
keycode 58 = Shift_Lock

Does anybody know a workaround for this?

Revision history for this message
Gary Wu (gary-wu) wrote :

Looking through various scripts (ckbcomp in particular), I found out that the problem was caused by the entry of

CHARMAP="UTF-8"

in /etc/default/console-setup, while a corresponding UTF-8.acm.gz does not exist in /usr/share/consoletrans/ as chkcomp was expecting. If I change the CHARMAP to use a different encoding that does exist in this directory, such as

CHARMAP="ISO-8859-1"

then the problem is fixed once you reboot or restart /etc/init.d/console-setup.

So, I don't know where the bug is... somehow my Edgy was installed with UTF-8 specified for the console encoding, but the file /usr/share/consoletrans/UTF-8.acm.gz was not installed.

-Gary

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

Thanks for your report. I'm going to make this a duplicate of bug 69725, as that has the clearest description so far.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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