From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Thibault Subject: Re: Bug#514464: caps lock led does not show up Date: Thu, 11 Jun 2015 17:37:55 +0200 Message-ID: <20150611153755.GA2247@type> 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> <20150611080809.GD3184@type.bordeaux.inria.fr> <20150611142803.GA3056@type.access.network> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20150611142803.GA3056@type.access.network> Sender: linux-kernel-owner@vger.kernel.org To: Anton Zinoviev , Dmitry Torokhov , Pavel Machek , Pali =?iso-8859-1?Q?Roh=E1r?= , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, rpurdie@rpsys.net, Greg Kroah-Hartman , 514464@bugs.debian.org List-Id: linux-input@vger.kernel.org Samuel Thibault, le Thu 11 Jun 2015 16:28:03 +0200, a =E9crit : > Samuel Thibault, le Thu 11 Jun 2015 10:08:09 +0200, a =E9crit : > > Putting > >=20 > > SUBSYSTEM=3D=3D"leds", ENV{DEVPATH}=3D=3D"*/input*::capslock", ATTR= {trigger}=3D"kbd-ctrlllock" > >=20 > > in /etc/udev/rules.d/50-leds.rules seems to be doing the work. >=20 > Except that it makes my system unbootable. For whatever reason, syste= md > indefinitely waits for the network to become available... ACTION=3D=3D"add", SUBSYSTEM=3D=3D"leds", ENV{DEVPATH}=3D=3D"*/input*::= capslock", ATTR{trigger}=3D"kbd-ctrlllock" works, however :) Samuel