Andrei, Top post of snippets below. I am increasinly of the mindest the DM should not be managing seats; no point in duplicating code for such.
Or maybe the DM should create and manage seats, and then we set XDG_SEAT logind is using and we have no logind or D-Bus integration, but that seems wrong, and from discussions, logind is the hardware manager, not the DM. Why I go back to, the DM should not manage seats, but listen for seat events and act accordingly, and via D-Bus or C-API, need to connect to logind session once it exists, after it exists; chicken and egg. On Sun, 2026-03-01 at 15:29 +0300, Andrei Borzenkov wrote: > 28.02.2026 10:28, Adrian Vovk wrote: > > > > I don't think the DM has the ability to create a seat. > > Quoting > https://www.freedesktop.org/software/systemd/man/latest/org.freedesktop.login1.html > > > Notice "to create a new seat". > > Hmm ... the description of ID_FOR_SEAT in the > https://www.freedesktop.org/software/systemd/man/latest/sd-login.html#Property%20ID_FOR_SEAT > > is wrong. It suggests that ID_FOR_SEAT is used to name new seat: > -- Sincerely, William L. Thomson Jr.
