On Fri, 25 Jan 2019 10:20:16 +0000 (GMT)
Russell Brown <russell@xxxxxxxxxxx> wrote:
> Hmmm.... tdekbdledsync is trying to control the wrong keyboard LEDs for
> remote displays.
>
> We have a number of remote users (XDMCP/tdm) and each one has a
> tdekbdledsync process running with /dev/tty0 and /dev/input/eventX open
> on the server (the machine hosting tdm) and not the remote workstation.
>
> This is obviously wrong.
>
> Ideally, tdekbdledsync should be smarter and not try to control the
> keyboard LEDs on remote displays but as it isn't, can I globally disable
> tdekdbledsync? (we don't run X on the main server console).
>
> I looked at the tdm source and in kgapp.cpp I see:
>
> if (trinity_desktop_synchronize_keyboard_lights) {
> kbdl = new TDEProcess;
> *kbdl << TQCString( argv0, strrchr( argv0, '/' ) - argv0
> + 2 ) + "tdekbdledsync"; kbdl->start();
> }
>
> but I can't find what sets "trinity_desktop_synchronize_keyboard_lights".
>
> Any pointers?
>
As this is not the only way tdekbdledsync is problematic i asked
before for an easy way to disable it but got no reply :( Now i just kill it
by cron job.
--
Nick Koretsky (nick.koretsky@xxxxxxxxx)
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
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
