> 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. * 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? * 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. ================================================== Bug reports involved: 928, kdm starts too early 925, [kdesktop] SAK driven secure dialog is not available for use 906, SAK realization is mostly buggy for KDM 898, tsak process taking 90-100% of CPU 894, TDM: Log file is never purged 884, tdmctl: Cannot connect socket '/var/run/xdmctl/dmctl-:0/socket' 667, kdm spawns kwin as root, keeps running after login 625, KDM is hard-coded to use /tmp rather than $TMP or $TMPDIR Thanks Tim! Darrell
