I launch the 2nd X server by logging in on a text console and typing:
$ xinit /usr/bin/xterm -- :1
Attaching the output of ck-list-sessions:
* After logging in at text console (e.g. Ctrl-Alt-F1) [can hear sound playing from 1st X server]
* After starting the 2nd X server, typed in the xterm that started with it [no sound]
* After executing ck-launch-session from the xterm [can hear sound again]
Further notes:
After changing to the text console, sound stops playing, but resumes when successfully logged in.
Don't know how relevant, but anyway: After executing ck-launch-session from the 2nd X server, the history of the xterm changes to match the one that I have in terminals of the 1st X server.
Hi James,
I launch the 2nd X server by logging in on a text console and typing:
$ xinit /usr/bin/xterm -- :1
Attaching the output of ck-list-sessions:
* After logging in at text console (e.g. Ctrl-Alt-F1) [can hear sound playing from 1st X server]
* After starting the 2nd X server, typed in the xterm that started with it [no sound]
* After executing ck-launch-session from the xterm [can hear sound again]
Further notes:
After changing to the text console, sound stops playing, but resumes when successfully logged in.
Don't know how relevant, but anyway: After executing ck-launch-session from the 2nd X server, the history of the xterm changes to match the one that I have in terminals of the 1st X server.