Hi all,
during the research around kdesktop_lock I found that kdesktoplockcontrol (formerly pipe, now socket) can never work. Pipe / socket is created in folder /tmp/tdesocket-global, but into this folder can enter and write 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 tdesocket-global 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.
Slavek
Much of this has been fixed in GIT. The pipes are rarely used, which is why they became non-functional without detection some time ago, but are part of the smart card login system.
Tim