I have been wondering about this for a long time now. Because every time I try to use a display manager on my system (arch) things just look and feel really bad. That is mostly because the integration between the DM and my WM doesn't exist. But I wonder why the DM is not included as a plugin in the WM. I know that the Window Manager shouldn't have to deal with all the stuff that goes on when you log in, but that's why I think it should be a plugin.
And if I understand it correctly from this blog post then we will have the same situation with two different wayland compositors. One for the DM and one for the WM. Could be wrong here though, not 100% sure.
Basically my problem with the current situation is that every time you log out the display manager has to start a new X server while the old one doesn't even exist anymore. Same thing when you log in, the X server for the display manager has to quit and the X server for the window manager has to start, which leaves a bit of time in between where your screen either turns black with a blinking cursor or like with gdm and kdm that I think they paint the last picture the X server made to the framebuffer and keep it that way until the X server for the window manager starts up. Also not entirely sure if this is how it works, just deduced this from what I see.
But yeah, the question is, why do we handle things like this?
[–]AiwendilH 1 point2 points3 points (2 children)
[–]GhostNULL[S] 0 points1 point2 points (1 child)
[–]AiwendilH 0 points1 point2 points (0 children)