One of the early ideas in Wayland development was the idea of a system compositor.  The system compositor sits below the user session and lets you switch between multiple sessions and manages screen saver and login screen.

It sounds like a good idea, but there's too much extra overhead and complexity there that we don't need.  There is also too much impedance mismatch between the API you want to present to a display server and to a user application to try to force it into the same protocol.

Instead, I'm now in favor of a more minimal solution, and while I've only been waving my hands about this, +David Herrmann has been busy working on it and wrote up a very good overview of the idea here.
Dear CONFIG_VT,
While juvenility made me miss your perseverance
and pride hid all your sway,
deep down you know it 'ready,
you're about to go away!

(summary of mostly high-level thoughts around using logind as session-manager; let the coding begin!)
Shared publiclyView activity