[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
shemgp, this is a different problem: see bug 84156. You can work around it by running 'sudo setupcon' once from a console after each boot. -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://bugs.launchpad.net/bugs/69725 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
I think this issue affects feisty too. console- setup_1.13ubuntu13_all.deb is installed but Caps Lock still doesn't work in the terminals. I've tried it in a P4 machine and two laptops. Also, pressing Caps Lock + any letter doesn't make it capital. my /usr/bin/ckbcomp lines 1925-1932 are: # A hack to work around a bug in the kernel/loadkeys # Disabled for Ubuntu because the cure is worse than the disease: # https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/69725 # However, Turkish still needs this behaviour. if (! $acm grep { $_ eq 'tr' } @layouts) { $xkbsym_table{'Caps_Lock'} = 'Shift_Lock'; $xkbsym_table{'ISO_Lock'} = 'Shift_Lock'; } I'm using kernel Ubuntu Kernel 2.6.20-15.27 Thanks for your help. -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://bugs.launchpad.net/bugs/69725 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
I think this issue affects feisty too. console- setup_1.13ubuntu13_all.deb is installed but Caps Lock still doesn't work in the terminals. I've tried it in a P4 machine and two laptops. Also, pressing Caps Lock + any letter doesn't make it capital. my /usr/bin/ckbcomp lines 1925-1932 are: # A hack to work around a bug in the kernel/loadkeys # Disabled for Ubuntu because the cure is worse than the disease: # https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/69725 # However, Turkish still needs this behaviour. if (! $acm grep { $_ eq 'tr' } @layouts) { $xkbsym_table{'Caps_Lock'} = 'Shift_Lock'; $xkbsym_table{'ISO_Lock'} = 'Shift_Lock'; } I'm using kernel Ubuntu Kernel 2.6.20-15.27 Thanks for your help. -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://bugs.launchpad.net/bugs/69725 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
console-setup (1.13ubuntu4) feisty; urgency=low * Include ro(std) in keymap tree, after talking with Eddy Petrişor. * Disable workaround in ckbcomp for the kernel not applying Caps Lock to non-ASCII letters; the cure is worse than the disease because it makes Caps Lock equivalent to Shift Lock (LP: #69725). * Install MyKeyboardNames.pl (built from /usr/share/X11/xkb) rather than KeyboardNames.pl (built from the out-of-date copy in Keyboard/ckb) as /usr/share/console-setup/KeyboardNames.pl (LP: #71864). -- Colin Watson [EMAIL PROTECTED] Fri, 5 Jan 2007 14:15:04 + ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) = Colin Watson Status: Confirmed = Fix Released -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://launchpad.net/bugs/69725 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
Yes, I saw that, thanks, but it's a red herring; CHARMAP is meant to be UTF-8, and there isn't supposed to be an ACM installed for UTF-8. Anton replied and told me (I hope he won't mind me reproducing his comment here): I think the only way to fix this problem is to patch the kernel. The problem is that when the keyboard is in Unicode mode CapsLock works only for the ASCII letters. For all other letters this key works only in non-Unicode mode and unfortunately for ckbcomp it is not easy to check whether the keyboard produces only ASCII letters. Compare also this patch we've had in console-tools for a long time: - 951_fix_unicode_loadkeys_capslock.patch: When loading unicode key maps, apply KT_LETTER to values in the range a-z or A-Z rather than KT_LATIN. This seems to be necessary to make Caps Lock work properly. More information is here: https://launchpad.net/distros/ubuntu/+source/linux- source-2.6.15/+bug/16638 -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://launchpad.net/bugs/69725 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69725] Re: Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock
** Attachment added: My /etc/default/console-setup file (as written by the upgrade from Dapper to Edgy) http://librarian.launchpad.net/4945568/console-setup -- Upgrade from dapper to edgy changed Caps_Lock to Shift_Lock https://launchpad.net/bugs/69725 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs