Why would one want to manipulate the leds through the window manager? I'm
sure there are valid reasons I just can't think of any off the top of my
head.
On Fri, Feb 19, 2016 at 4:40 AM, Nick Koretsky <nick_koretsky(a)ukr.net>
wrote:
On Fri, 19 Feb 2016 03:20:18 +0100
Slávek Banko <slavek.banko(a)axis.cz> wrote:
> OK so I don't know what tdekbdledsync is
for but that was definitely
the
problem.
I will write a script to kill that then turn on the back light
thanks. I will also keep an eye out for any downsides to killing that
process.
Thanks all.
tdekbdledsync has the task to synchronize the LED status between the
Xserver and the keyboard.
And as a side effect it complete blocks any attempts to manipulate LEDs
from software. Including f.e. grp_led option to xkb. Unsynchronized LEDs is
a very uncommon problem, i would say much more uncommon than using of
grp_led. So starting it should be at least optional.
--
Nick Koretsky (nick.koretsky(a)gmail.com)
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
John Pisini
Systems Administrator
TFCCS
617-450-3988
Disclaimer for email:
The information contained in this electronic message and any attachments to
this message is intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. This e-mail is not
intended to, and shall not, constitute an electronic signature giving rise
to a binding legal contract, unless expressly stated otherwise in the body
of the e-mail by the sender.