Specification for org.freedesktop.DisplayManager DBus API?
math.parent at gmail.com
Sun Mar 15 13:43:28 PDT 2015
2015-03-15 18:36 GMT+01:00 David Herrmann <dh.herrmann at gmail.com>:
> Our plan with logind is to avoid any display-manager API. Instead, we
> kinda want this to be 'session-activated'. That means, by using the
> SwitchTo() API in logind, you can activate *any* VT (or using chvt, in
> case CONFIG_VT=y). You can now configure service symlinks which are
> activated by logind if a given VT position is activated and no session
> is running on it. Therefore, a simply VT-switch to an empty session
> will spawn your login-manager. Once the login manager is done, the
> session can take over the same VT (or spawn on a new one, it's up to
> the login-manager to decide).
> This is basically what we already do with autovt at .service to spawn
> gettys on demand.
> This allows us to avoid running a login-manager on a fixed VT.
> Instead, the user simply selects the VT where it wants to login and
> the login-manager is spawned there. Imo, this feels more natural,
> instead of having to 'know' where the login-manager is running and
> switching to that VT. Furthermore, you now have control on which VT
> your session is spawned, instead of a random VT.
> Once kdbus is done, I intend to go ahead and implement those ideas.
> We've been talking about this for way to long without any code showing
> up. Sorry for that.
This looks great to me. But how to know if the user wants a terminal
or graphical session?
VT > =7?
More information about the xdg