> OK, sounds reasonable, though I would rather disable the
> TSAK checkbox and display a warning message next to it, in order to provide
> more immediate feedback as to the state of the user's system.

That sounds better. All we need is a mechanism that makes the uinput connection obvious to the user. I never would have figured that out. Well, maybe --- after many four letter words and scouring the source code. :) A context sensitive warning directly in the KControl dialog will do nicely.

> > BTW, the help handbook has nothing about TSAK. Nada. :)
> 
> Probably because I still have not figured out how to use the
> docbook stuff, nor do I have plans to do so. :-)

Send me the text. :)

We don't need a book. Just a few paragraphs. I'll merge the text into the existing TDM help file. Basic description for now:

What is TSAK.
When to configure.
Requirements/dependencies.
How to use/what users see.

> I'll start working on these ASAP...
> 
> Thanks for the detailed report!

Par for the course. :) We're in good shape. Most of those details were exhaustive ways of describing the booginess of the Lock Session dialog. The housekeeping and xsession messages should be straightforward fixes. I'll guess with the two xsession messages that they appear once the code determines useSAK=true and can't find TDM. A simple error check routine would eliminate the messages such as whether TDM is running.

Darrell