So, what I think happens is that ck creates a session for you on
the text console. You then launch and X session from it, and switch
to it, away from the VT that the session is associated with, so
it thinks there are no active sessions.
You can try running
$ ck-launch-session xinit /usr/bin/xterm -- :1
or
$ xinit ck-launch-session /usr/bin/xterm -- :1
to force a new session.
Fixing this properly would require nested session support in ck I think.
Hi,
So, what I think happens is that ck creates a session for you on
the text console. You then launch and X session from it, and switch
to it, away from the VT that the session is associated with, so
it thinks there are no active sessions.
You can try running
$ ck-launch-session xinit /usr/bin/xterm -- :1
or
$ xinit ck-launch-session /usr/bin/xterm -- :1
to force a new session.
Fixing this properly would require nested session support in ck I think.
Thanks,
James