Collation of TSAK/TDM related issues (there are overlaps in descriptions but that does not mean the same exact problem):
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
================================================== Direct TSAK issues:
* TSAK demands 90-100% CPU.
* High CPU consumption on wait SAK.
* TSAK/TDM performs no housekeeping to remove pipe/socket files: 1) During a reboot/halt (when TDM terminates) 2) X server restart (which TDM allows) 3) When a user disables TSAK in KControl (tdmrc:UseSAK=false)
* Restarting X server or TSAK ignores the tdmrc:UseSAK=false, using the existing pipe/socket files instead and keeps running even when explicitly disabled in tdmrc.
* When building tdebase without TSAK support (-DBUILD_TSAK=OFF), and tdmrc:UseSAK=false, TDM starts with the dialog to press Ctrl-Alt-Del. That should not happen.
* Disabling TSAK in tdmrc (UseSAK=false) does not work.
* Exit from wait dialog by Ctrl+Alt+Del does not work.
* Some people cannot obtain access to the TDM login dialog when pressing Ctrl-Alt-Del.
* TSAK ownership of /tmp/tdesocket-global is assigned to the system's primary login account. Ownership of that directory is determined by the account UID listed in the tdmrc MinShowUID key and then that account number is grabbed from /etc/passwd.
* xsession message of "[kdesktop] SAK driven secure dialog is not available for use (retcode %d)" appears although TDM is not running when using startx.
================================================== Related to TDM and TSAK:
* 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.
================================================== TDM specific:
* TDM starts too early
* TDM log files never purged.
* TDM spawns twin as root, keeps running after login
I hope this helps. :)
Darrell
<snip>
I hope this helps. :)
Darrell
Yes it does, but YIKES that's a lot of problems! :-)
A few of the highest priority problems should already be fixed in GIT, but there are a slew of lower-priority (FIFO ownership/location, etc.) problems that are not yet fixed.
I think it would be helpful if we were to re-file each of the issues you mentioned above as a separate bug report, then point the original (combined) reports to block on any of the new (separate) reports that apply. Otherwise it will be very difficult to keep track of what was fixed and what still needs to be done!
Tim
Yes it does, but YIKES that's a lot of problems! :-)
A few of the highest priority problems should already be fixed in GIT, but there are a slew of lower-priority (FIFO ownership/location, etc.) problems that are not yet fixed.
I think it would be helpful if we were to re-file each of the issues you mentioned above as a separate bug report, then point the original (combined) reports to block on any of the new (separate) reports that apply. Otherwise it will be very difficult to keep track of what was fixed and what still needs to be done!
Might seem like a lot, but several issues likely need little more than testing the run level or whether TDM is running.
Regarding the FIFO stuff, checking tdmrc:useSAK as the first step and basic housekeeping resolves several issues.
After collating the list I don't think we're in horrible or overwhelming shape. All I see at this point is needing some fine-tuning --- as is the typical bug quashing process for new code. We'll get there much sooner than later. :)
The biggest fix is that tdmrc:useSAK=false is always honored. The quiets 80% or more of all users. :)
Let me finish my build run and then test the latest patches. Then I can assess into separate new reports.
Darrell
-
Darrell Anderson -
Timothy Pearson