tdekbdledsync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

-- 
 Regards,
     Russell
 --------------------------------------------------------------------
| Russell Brown          | MAIL: russell@xxxxxxx PHONE: 01780 471800 |
| Lady Lodge Systems     | WWW Work: http://www.lls.com              |
| Peterborough, England  | WWW Play: http://www.ruffle.me.uk         |
 --------------------------------------------------------------------

---------------------------------------------------------------------
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




[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux