On Friday 16 of August 2013 23:23:57 Darrell Anderson wrote:

We raised this observation in past discussions and bug reports.

I am not using TDM. I start X from the command line with startx. Yet I see /tmp/tdesocket-global being created with the login user having full ownership to the directory. The logged-in user can view the contents of the directory, which is always empty.

Why is the /tmp/tdeglobal-socket directory being created when TDM is not being used? What global socket connections are required when Trinity is run without TDM or in run level 3?

Darrell

I believe that this is exactly what I pointed out earlier: http://trinity-devel.pearsoncomputing.net/?0::11083

When using TDM, folder /tmp/tdesocket-global is created by root and users does not have access into this folder => it is the correct behaviour. But user cannot create there kdesktoplockcontrol:

[kdesktop_lock] Warning: unable to create control socket '/tmp/tdesocket-global/kdesktoplockcontrol-0'. Interactive logon modules may not function properly.

When TDM is not in use, folder /tmp/tdesocket-global is created by first logged user, but it is wrong in principle.

Slavek --