On Fri, 17.01.14 13:01, Carlos Garnacho ([email protected]) wrote: > > Hey Lennart :), > > On vie, 2014-01-17 at 12:04 +0100, Lennart Poettering wrote: > > On Fri, 17.01.14 12:01, Carlos Garnacho ([email protected]) wrote: > > > > > This helper program checks the leds available on keyboard devices > > > and exports these as list of keywords in the ID_INPUT_KEYBOARD_LEDS > > > property. The new .rule ensures this helper program runs at the time > > > any keyboard is detected/plugged. > > > > What's the usecase for this? > > Complementing this code, I've got a gnome-settings-daemon patch to show > an OSD to hint about *Lock keys being pressed when the keyboard in > question does not have leds to tell so. The laptop I got recently has > none, and it buggers me when I start yelling without noticing.
Hmm, so the idea here is to attach this information to the udev devices, so that it is available unprivileged? Wouldn't it be more accurate to expose this information via xinput? (Not saying that we shouldn't merge this into udev anyway, just asking...) Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
