[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#535997: marked as done (Can not assign arbitrary modifiers to the keyboard leds)

Your message dated Sun, 2 May 2010 23:24:13 +0200
with message-id <20100502212413.GA5449@galadriel.inutil.org>
and subject line Should be directed upstream
has caused the Debian Bug report #535997,
regarding Can not assign arbitrary modifiers to the keyboard leds
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
535997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535997
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-latest-2.6
Severity: wishlist

Hi!

The keyboard driver of Linux supports several modifiers: shift, altgr, 
control, alt, shiftl, shiftr, ctrll, ctrlr and capsshift.  Due to some 
limitations of the method CapsLock is implemented in the kernel, for 
several languages it is necessary some other modifier to be used instead 
of CapsLock.  For example console-setup often uses ctrll instead of 
capslock and the whole purpose of capsshift is to be used as a 
replacement for capslock.  Unfortunately currently it is impossible to 
tell the kernel to display the state of the ctrll or capsshift modifier 
with the CapsLock led.  As a result the CapsLock led doesn't work for 
keyboard layouts that can not use the CapsLock modifier.

A related bug to this one is #514464.

Anton Zinoviev

--- End Message ---
--- Begin Message --- 
Should be directed upstream.

--- End Message ---
Reply to: