This was fixed in LTSP 5.2. `su` was used instead of `ck-launch-session`, along with $CKCON_X11_DISPLAY and $CKCON_X11_DISPLAY_DEVICE pam environment parameters, so that now LTSP fat clients properly get an active CK session.
Closing in LTSP, the problem is still there on consolekit though.
This was fixed in LTSP 5.2. `su` was used instead of `ck-launch- session` , along with $CKCON_X11_DISPLAY and $CKCON_ X11_DISPLAY_ DEVICE pam environment parameters, so that now LTSP fat clients properly get an active CK session.
Closing in LTSP, the problem is still there on consolekit though.