>> Bug fixed in GIT hash 06adb18. Sometimes it is better >> to look at things in the morning instead of late at night. ;-) > > Been there, done that! :) > > Latest patch: > > http://humanreadable.nfshost.com/trinity/build_logs/tsak.png > > Yay! > > Regarding the original list of TSAK/TDM issues I posted Wednesday, 18 > April. We have made great progress and the following list is muuuuuuuuch > shorter. :) > > * TSAK demands 90-100% CPU / High CPU consumption on wait SAK. > Need testing by those who reported the problem. (I never experienced the > problem.) > > * xsession message of "[kdesktop] SAK driven secure dialog is not > available > for use (retcode %d)" appears although TDM is not running when using > startx. This is debug spew from kdesktop and should be ignored unless you are trying to debug the Secure Dialog/Desktop Lock system. The best way to fix this is probably to make the printf() into a kdDebug so that it does not pollute .xsession_errors. Thoughts? > * When starting X from startx (TDM is not running) the message > "tdmctl: Cannot connect socket '/var/run/xdmctl/dmctl-:0/socket'" > appears. There should be no tdmctl/TSAK related messages when using > startx. > > * Both calls to tdmctl in tdmtsak use the format "tdmctl list" yet there > is no > "list" option in tdmctl --help. What is the "list" parameter supposed to > do? IIRC "list" forces tdm to list all active sessions. It may be undocumented, but is used internally in the code. > * TDM creates nominal profile directories in /tmp. All such directories > use a > numeric name string. TDM runs as non-user, but should not be creating > any > profile directories. Not needed and the profile directories are never > purged. > Never happened in KDE3. This is due to twin as I mentioned earlier. In order to provide a managed window environment for TDM twin has to be launched, and twin expects to see DCOP running, so it is launched as well. The "profile directory" created consists of a number of DCOP sockets and related files. I do not yet know what the best way to deal with this is. I have also repaired the desktop lock in GIT hash 50739c9--you should no longer have the desktop and icon problems you were experiencing earlier. If they do persist please let me know! Tim