>> You will only see the dialog if: >> 1.) It is turned on in tdmrc via tdmrc:useSAK=true as you stated >> 2.) Your system fully supports tsak; this usually means that you need to >> load the uinput kernel module on Linux. Trying to run >> /opt/trinity/bin/tsak manually (as root) will give you the >> exact reason for any failures encountered. > > Perhaps a couple of changes: > > * The What's This popup should provide the uinput information. > > * Whenever a user enables the SAK check box in KControl, upon pressing the > Apply button the code should determine whether uinput is loaded. If not, > provide an informational OK dialog that uinput needs to be loaded. If > uinput is loaded then don't bother with a dialog. 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. > 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. :-) <snip> > Summary: > > Lots of details here, initially looks overwhelming, but good progress > overall. Mostly this narrows to a few issues. > > * Adding informational aides about uinput. > > * What is happening with the TSAK Lock Session dialog with why the desktop > icons disappear, the desktop context menu > will not appear, and the user can't logout thereafter. > > * Remove the two xsession messages when logging in from the command line. > > * Improve housekeeping by removing tsak.lock: 1) upon a reboot (TDM should > do this), 2) disabling TSAK from KControl. > > * I do not recommend automatically loading uinput for the user because > with the next reboot the module again needs to be > loaded. The distros all differ with how that is accomplished. Possibly a > nice aide would be whenever the system starts > and TDM detects the status of useSAK=true, and uinput is not loaded, > perhaps an informational "OK" dialog appears > informing the user. The uinput requirement is just not obvious anywhere. > > > Darrell I'll start working on these ASAP... Thanks for the detailed report! Tim