Hello, You mentioned up the email chain that there is no misconception. There _is_ a misconception. That is becoming increasingly clear.
A logind session is not a service. It is not a program that runs. You can't talk to it via PID because there's nothing logind related on that PID. There's no such thing as connecting to a logind session. A logind session is an entry in a hash table in the main logind system-level daemon. Full stop. That's how it's represented in memory. There's no process, no nothing. The logind session is associated with a process. This is called the "session leader". The session exists for as long as the session leader exists. But the session leader plays exactly 0 role in managing the session. All of the management is centralized in logind, the system-level daemon Until you understand this, there seems to be no point discussing in any other direction. This is a fundamental error in your conception about logind and until it's corrected there's no way to have a conversation about this, we'd only talk past each other forever. Perhaps the confusion is because of the way consolekit works. It seems that there is some intermediate consolekit process that you used to spawn. There is no such thing in logind. You also keep mentioning sd_pid_get_session. Question is: why? I don't understand why you need to call this function. Best, Adrian On Sun, Mar 1, 2026, 23:40 William L. Thomson Jr <[email protected]> wrote: > On Sun, 2026-03-01 at 20:19 -0500, William L. Thomson Jr wrote: > > > > Again I come back to, how is all this supposed to work? > > > > This is still my main question overall. At the moment, it seems the > attempted approach is to connect to a logind session, but this maybe > incorrect. > > I was thinking to create a logind session via D-bus in some manner for > years, but another stepped up and did a C-API approach, and I am just > trying to integrate that with existing DM code, and get their > contribution working, if it can. > > It seems, that I should be interacting with the logind daemon/service > vs the sessions that get created. Since the DM is supposed spawn > greeters on any seats as they show up. > > I have to look more into the code, but I thought the seat only showed > at logind session creation, but maybe the logind daemon/service is > aware prior to session creation. > > > Anyway, back to the main point, the current approach maybe incorrect, > why asking how its all supposed to work. It seems this is all for > multi-seat, because for single, just hard coding seat0 in the DM works > just the same with logind. Seats being Wayland specific, unless X11 > does something someday with seats. > > > Thank you to all for replies and information, I do appreciate it! > > > -- > Sincerely, > William L. Thomson Jr. >
