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?
On Fri, 25 Jan 2019 10:20:16 +0000 (GMT) Russell Brown russell@lls.lls.com 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 wrote:
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.
What happens if you replace it with empty executable file (as work around) - something like
#!/bin/sh exit 0
Secondly would you please open a request somewhere, as I am pretty sure if this is not documented no one will take care and if you have a request, provide the number as reference.
regards
On Fri, 25 Jan 2019 14:21:56 +0100 deloptes deloptes@gmail.com wrote:
Nick Koretsky wrote:
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.
What happens if you replace it with empty executable file (as work around) - something like
#!/bin/sh exit 0
The problem is you have to redo that on every update.
Secondly would you please open a request somewhere, as I am pretty sure if this is not documented no one will take care and if you have a request, provide the number as reference.
There is a bug report with a request for option to disable it from 2014.. https://bugs.trinitydesktop.org/show_bug.cgi?id=1834
Nick Koretsky wrote:
The problem is you have to redo that on every update.
of course :)
Secondly would you please open a request somewhere, as I am pretty sure if this is not documented no one will take care and if you have a request, provide the number as reference.
There is a bug report with a request for option to disable it from 2014.. https://bugs.trinitydesktop.org/show_bug.cgi?id=1834
I'll ask Michele to include it into one of the milestones for the next releases. Obviously it was missed.
regards
Nick Koretsky wrote:
There is a bug report with a request for option to disable it from 2014.. https://bugs.trinitydesktop.org/show_bug.cgi?id=1834
FYI: Copy/Paste response from Michele
Added to R14.1.0 list given that a crash and high CPU usage is not very good :-) Cheers Michele
-
deloptes -
Nick Koretsky -
Russell Brown