I have some ideas for a nested-X-server seat module for LightDM, and I really appreciate your feedback:
- Introduce new modules x-server-nested-{local,remote,xvnc} (or something similar).
NOTE: A nested X server could be a Xephyr server or a real X server with "nested" video driver.
- Introduce new modules seat-{xlocal,xremote,xvnc}-nested corresponding to x-server-nested-* above.
- [REALLY NEEDED?] Introduce a new module x-server-host (or extend x-server-local), which should launch a X server with no greeter, spanning all available monitors.
- When a seat-x-nested is started, it should check if there's a x-server-host already running, on top of which it can launch a x-server-nested instance. If not, it should request LightDM to launch a x-server-host for it.
- LightDM should monitor the list of seat-x-nested instances running on top of a given x-server-host. When the last seat-x-nested is disconnected, the x-server-host should be (optionally) terminated.
- The seat-x-nested module should take care of placing the x-server-nested window in the right position. Until Xephyr gets a proper way to set its window placement (like a -geometry option), it needs to be made via wmctrl or something similar.
Hi there!
I have some ideas for a nested-X-server seat module for LightDM, and I really appreciate your feedback:
- Introduce new modules x-server- nested- {local, remote, xvnc} (or something similar).
NOTE: A nested X server could be a Xephyr server or a real X server with "nested" video driver.
- Introduce new modules seat-{xlocal, xremote, xvnc}-nested corresponding to x-server-nested-* above.
- [REALLY NEEDED?] Introduce a new module x-server-host (or extend x-server-local), which should launch a X server with no greeter, spanning all available monitors.
- When a seat-x-nested is started, it should check if there's a x-server-host already running, on top of which it can launch a x-server-nested instance. If not, it should request LightDM to launch a x-server-host for it.
- LightDM should monitor the list of seat-x-nested instances running on top of a given x-server-host. When the last seat-x-nested is disconnected, the x-server-host should be (optionally) terminated.
- The seat-x-nested module should take care of placing the x-server-nested window in the right position. Until Xephyr gets a proper way to set its window placement (like a -geometry option), it needs to be made via wmctrl or something similar.
Some of these ideas are inspired in https:/ /launchpad. net/multi- seat-xephyr