23 Apr
2012
23 Apr
'12
2:09 p.m.
* 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.
Likewise with this message. The message only appears in command line login mode because
TDM is again not running. I have yet to see the message when testing in graphical login
mode.
* 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.