*** This bug is a duplicate of bug 69725 ***
Thanks for your report. I'm going to make this a duplicate of bug 69725,
as that has the clearest description so far.
** This bug has been marked a duplicate of bug 69725
Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
--
caps lock
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?
--
caps lock led doesn't work on the virtual terminals
https://launchpad.net/bugs/63104
--
ubuntu-bugs mailing list
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
** Changed in: Ubuntu
Sourcepackagename: None = console-setup
--
caps lock led doesn't work on the virtual terminals
https://launchpad.net/bugs/63104
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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
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.
** Changed in: Ubuntu
Status: Unconfirmed = Confirmed
--
caps lock led doesn't
this would be due to kmilo having not been started, which deals with all
those special keys, i expect. or a part of X.
--
caps lock led doesn't work on the virtual terminals
https://launchpad.net/bugs/63104
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
