Message: previous - next
Month: May 2013

Re: [trinity-devel] kdesktoplockcontrol can never work

From: "Darrell Anderson" <darrella@...>
Date: Wed, 15 May 2013 10:44:13 -0500
>during the research around kdesktop_lock I found that 
>(formerly pipe, now socket) can never work. Pipe / socket is 
>created in 
>folder /tmp/tdesocket-global, but into this folder can enter and 
>only 'root'. The folder is created with permissions 0644, which is 
>a bit 
>unusual for the folders.
>I also noticed (when I was allowed to write to the folder 
>also for others) that kdesktoplockcontrol and 
>kdesktoplockcontrol_out are 
>created but never removed.
>Please can anyone confirm my findings?
>How kdesktoplockcontrol was intended?
>Currently obviously can never work.

I'm using pre R14 from GIT. I start X from the command line with 
startx and not in graphical mode with TDM. Therefore during a 
normal user session, /tmp/tdesocket-global does not exist because I 
am not using TDM.

When I lock the screen I see the following created:



I do not see any files named kdesktoplockcontrol or 

There are no files in /tmp/tdesocket-global.

/tmp/tdesocket-global is created with 0644 $USER:$USER permissions 
yet through konqueror and the command line I cannot access the 

From my perspective, the /tmp/tdesocket-global directory should 
never be created when a user locks the screen, which is a user-
based action, not global. Second, seems to me whenever 
/tmp/tdesocket-global is created the ownership should always be 
root:root, not $USER:$USER. Third, permissions should be 0755, not 

I remember raising the topic of housekeeping a long time ago. When 
I experiment with TDM to help with nominal testing, I notice that 
/tmp/tdesocket-global remains across a reboot, as does files in 
that directory.