I have a CM devastator keyboard with back lighting. This keyboard uses the scroll lock key to turn the light on and off. On my system running Ubuntu under other desktop environments like Mate or KDE I can turn the back light on using xset led 3 and I usually have it scripted to turn on after I log in. Under Trinity doing xset led 3 causes the keyboard to flash really quickly once and then the light goes off. Is there something holding the keyboard under Trinity? Is there a way to use the back light?
Am Donnerstag, 18. Februar 2016 schrieb Pisini, John:
I have a CM devastator keyboard with back lighting. This keyboard uses the scroll lock key to turn the light on and off. On my system running Ubuntu under other desktop environments like Mate or KDE I can turn the back light on using xset led 3 and I usually have it scripted to turn on after I log in. Under Trinity doing xset led 3 causes the keyboard to flash really quickly once and then the light goes off. Is there something holding the keyboard under Trinity? Is there a way to use the back light?
is "Secure Attention Key" in the session management turned on or off?
I go to TDE components > session manager and I don't see anything like that. Am I in the wrong area?
On Thu, Feb 18, 2016 at 8:36 AM, Dr. Nikolaus Klepp office@klepp.biz wrote:
Am Donnerstag, 18. Februar 2016 schrieb Pisini, John:
I have a CM devastator keyboard with back lighting. This keyboard uses
the
scroll lock key to turn the light on and off. On my system running Ubuntu under other desktop environments like Mate or KDE I can turn the back
light
on using xset led 3 and I usually have it scripted to turn on after I log in. Under Trinity doing xset led 3 causes the keyboard to flash really quickly once and then the light goes off. Is there something holding the keyboard under Trinity? Is there a way to use the back light?
is "Secure Attention Key" in the session management turned on or off?
-- Please do not email me anything that you are not comfortable also sharing with the NSA.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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
Never mind I found it under Login Manager > appearance, It is not on should it be? I won't be back in front of that system until 8PM tonight so I can't test until then.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 02/18/2016 08:53 PM, Pisini, John wrote:
I go to TDE components > session manager and I don't see anything like that. Am I in the wrong area?
System Administration -> Login manager and Appearance & Themes -> Screen saver
Cheers Michele
I have my own customized version that I use across multiple systems, so while I don't have that keyboard here at work I have the same OS with the same settings and they are both unchecked. Should I try enabling them?
On Thu, Feb 18, 2016 at 10:04 AM, Michele Calgaro michele.calgaro@yahoo.it wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 02/18/2016 08:53 PM, Pisini, John wrote:
I go to TDE components > session manager and I don't see anything like
that. Am I in the wrong area? System Administration -> Login manager and Appearance & Themes -> Screen saver
Cheers Michele -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBCgAGBQJWxd2BAAoJECp1t8qK3tXPI6oP/RhaWoQe0J/Ge3pjtn6AejiO D1Uo5ls4mM2A061+l3l21QixTxsmjSKVA8yOkkke86/nAi6Hn9TCeWRhhLKbHn36 ohfNOT0OSZgMLZ20K3kmnBfdvuDHtfV2j7FROE9+TK+qSJ6ei37cPKOig7VFc4Kq X+ydmSNVjEskrhFQgnSGjmoCy4YMK0dd36AOcQUsnA8R96gA7EPS6iYiWXkNQLdU 5kPbLZfY+nnkba5R/fZYUDbNcpypIyxySo+BSdY6+LpPIzuQqG88r6+UOz1Zh9R7 YzP/FiAs18ob9qSjgyFqpyw8Kt8YARorbBr/fRaCVI1w9djU3VfL63n6w9tAbfbq s8gbmZD3J+m2KcBneohhI0dDN6i6GaS1/m9AWJsXya45z1Qbq1+ov19GJDgaEoNq Mmijh0WgkGCEut5ZpFKGWbfpRF73jbYeZiMXNxpazn/spYlbsjNRg1GwRYkJY6sh owyGYBfD83Nvoz8xVaX36dLjX2ulqnA0MyAWbE1fo8Smyid6x7+/D1jURzXDVPEk 6PznZ3p1FrPaE7XnHLxeRG4LV8tSn+ggNJb8b2YODtXQWAcSGVpFRQxBLbXMFIWo fERXotKYHD1huE0pJytctR8bCbugddRGMKmdeHyTXAMmmlGCEMqoYr9k5K71dck+ WO7QheDnSILVItK8+GA+ =c7w9 -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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
On Thu, 18 Feb 2016 08:29:50 -0500 "Pisini, John" pisinij@csps.com wrote:
I have a CM devastator keyboard with back lighting. This keyboard uses the scroll lock key to turn the light on and off. On my system running Ubuntu under other desktop environments like Mate or KDE I can turn the back light on using xset led 3 and I usually have it scripted to turn on after I log in. Under Trinity doing xset led 3 causes the keyboard to flash really quickly once and then the light goes off. Is there something holding the keyboard under Trinity? Is there a way to use the back light?
I have suspicion that this is caused by tdekbdledsync. Try killing it. This daemon is extremely weird solution to a very uncommon problem and for whatever reason AFAIK there is no way to disable it "correctly". I have
sudo killall tdekbdledsync
in autostart to deal with this bullshit
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.
On Friday 19 of February 2016 02:43:50 Pisini, John 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.
Yes, it is true that the process runs automatically and is not a configuration option to prevent it. Instead of killing the process you can try (on Debian and Ubuntu) blocking:
dpkg-divert --local --rename /opt/trinity/bin/tdekbdledsync ln -s /bin/true /opt/trinity/bin/tdekbdledsync
Thank you. I will try that out. On Feb 18, 2016 9:20 PM, "Slávek Banko" slavek.banko@axis.cz wrote:
On Friday 19 of February 2016 02:43:50 Pisini, John 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.
Yes, it is true that the process runs automatically and is not a configuration option to prevent it. Instead of killing the process you can try (on Debian and Ubuntu) blocking:
dpkg-divert --local --rename /opt/trinity/bin/tdekbdledsync ln -s /bin/true /opt/trinity/bin/tdekbdledsync
-- Slávek
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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
On Fri, 19 Feb 2016 03:20:18 +0100 Slávek Banko slavek.banko@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.
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@ukr.net wrote:
On Fri, 19 Feb 2016 03:20:18 +0100 Slávek Banko slavek.banko@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@gmail.com)
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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
On Friday 19 of February 2016 02:43:50 Pisini, John 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.
Incidentally: In any case, do not forget to fill the bug report!
-
Dr. Nikolaus Klepp -
Michele Calgaro -
Nick Koretsky -
Pisini, John -
Slávek Banko