Bug#514464: caps lock led does not show up
- To: Anton Zinoviev <anton@lml.bas.bg>
- Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, Pavel Machek <pavel@ucw.cz>, Pali Rohár <pali.rohar@gmail.com>, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, rpurdie@rpsys.net, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, 514464@bugs.debian.org
- Subject: Bug#514464: caps lock led does not show up
- From: Samuel Thibault <sthibault@debian.org>
- Date: Thu, 11 Jun 2015 10:08:09 +0200
- Message-id: <[🔎] 20150611080809.GD3184@type.bordeaux.inria.fr>
- Mail-followup-to: Samuel Thibault <sthibault@debian.org>, Anton Zinoviev <anton@lml.bas.bg>, Dmitry Torokhov <dmitry.torokhov@gmail.com>, Pavel Machek <pavel@ucw.cz>, Pali Rohár <pali.rohar@gmail.com>, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, rpurdie@rpsys.net, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, 514464@bugs.debian.org
- Reply-to: Samuel Thibault <sthibault@debian.org>, 514464@bugs.debian.org
- In-reply-to: <[🔎] 20150609160339.GB26687@logic.fmi.uni-sofia.bg>
- References: <1433799790-31873-1-git-send-email-dmitry.torokhov@gmail.com> <20090205113908.GA14224@const.inria.fr> <[🔎] 20150609141723.GE3045@type> <[🔎] 20150609160339.GB26687@logic.fmi.uni-sofia.bg>
Hello,
Anton Zinoviev, le Tue 09 Jun 2015 19:03:39 +0300, a écrit :
> On Tue, Jun 09, 2015 at 04:17:23PM +0200, Samuel Thibault wrote:
> >
> > Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit :
> > > If user wants all keyboards to light up CapsLock LED when VT state locks
> > > CtrlL modifier they need to write a udev rule or similar to set up
> > > "kbd-ctrlllock" trigger for all appearing "input%::capslock" LED class
> > > devices.
> >
> > Anton, this is the interface proposed by the input maintainer, Dmitry,
> > to change which modifiers gets to light the keyboard LEDs (the exact
> > names may change, but the principle should be firm). I know this is
> > inconvenient for console-setup for handling hotplugged keyboards,
>
> Ok, the inconvenience is not a problem. The problem is I don't
> understant the meaning of this. :)
>
> Is there some documentation or a sample code I can read?
Putting
SUBSYSTEM=="leds", ENV{DEVPATH}=="*/input*::capslock", ATTR{trigger}="kbd-ctrlllock"
in /etc/udev/rules.d/50-leds.rules seems to be doing the work. It'd be
good to include this in the documentation along the patch.
Samuel
Reply to: