On a previous post I got sometime ago from the bugzilla someone had discovered what the problem was about.... I think. Let me write it here for you (in case you haven't gotten it):
________________________________________________________________________ from Gary Wu <[EMAIL PROTECTED]>: Nov 6 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. ________________________________________________________________________ That's what he wrote. Hope it helps you solve the problem. On 12/4/06, Colin Watson <[EMAIL PROTECTED]> wrote: > I can't find out anything about what this kernel/loadkeys bug might have > been. I've mailed Anton upstream to see if he remembers. > > ** Changed in: console-setup (Ubuntu) > Importance: Undecided => High > Status: Unconfirmed => Confirmed > > -- > Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock > https://launchpad.net/bugs/69725 > -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://launchpad.net/bugs/69725 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
