A partial solution for bug 1685 is to provide a tool which only deals with the environment. In 4.3.0, we will save the environment to ${TLSESSIONDATA}/xstartup.env. What's missing is a tool which can execute a command in this environment. We also need to deal with the problem that, currently, xstartup.env is created from the "env" output, which does not correctly handle environment variables which contains embedded newlines etc.
Implemented in 29388.
Documented and tweaked in r29389, r29390. Suggested test cases: * Check that xstartup.env is created. Contents should be what "env -0" produces. * tl-notify * Executing a command outside the session: tl-env -d xterm
Verified using ThinLinc build 4505, works as expected. However tl-notify have double meaning error reporting when xstartup.env is removed from session directory; /opt/thinlinc/sbin/tl-notify hello error: failed to read xstartup.env ([Errno 2] No such file or directory: '/var/opt/thinlinc/sessions/cendio/1/xstartup.env') Message sent to 1 sessions on this agent.
(In reply to comment #3) > Verified using ThinLinc build 4505, works as expected. > > However tl-notify have double meaning error reporting when xstartup.env is > removed from session directory; > > /opt/thinlinc/sbin/tl-notify hello > error: failed to read xstartup.env ([Errno 2] No such file or directory: > '/var/opt/thinlinc/sessions/cendio/1/xstartup.env') > Message sent to 1 sessions on this agent. Should be a problem introduced by bug 5153.
(In reply to comment #4) > Should be a problem introduced by bug 5153. Closing due to the issue is handled on bug #5153