Message: previous - next
Month: April 2012

Re: First report: TSAK/TDM related issues

From: Calvin Morrison <mutantturkey@...>
Date: Thu, 19 Apr 2012 11:52:31 -0400
> 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.

I am wondering if this is actually a problem with KDesktop, the desktop 
icons have had plenty of problems in the past and do as of 3.5.13

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

Again, all distros handle the /tmp different, so the best way would be 
to check if those file exist during the startup of the computer. if it 
already exists, delete and create a new one.

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

I mean TDM/TSAK typically starts on boot, so I see the module being 
loaded by TDM as fine. Xorg loads kernel modules for example, for the 
drivers and input if they are not there. TDM should also load neccessary 
modules. I don't think we need to say "Uinput loaded" in a dialog, if 
anything just a output to a log saying that it was loaded. All current 
linux systems use modprobe so I think that's fairly straight across the