On Fri, 25 Jul 2025 at 04:17, Andrew Bower <[email protected]> wrote: > 1. Unitialised 'sessions' variable is a a bug on all systems which leads > to a segfault on some. I'm now tagging this bug as having a patch. > Yep, that makes sense. Upstream have this set to 0 so it got missed.
> 2. elogind not being queried. Is this an elogind issue? Should it give a > different answer to sd_booted() or is this the wrong way to detect the > seat management capability? 'who' does not have this problem - it > somehow queries elogind anyway. > elogind always returns 0 for sd_booted(). Maybe who doesn't look at sd_booted() and directly goes to sd_get_sessions()? > procps then resorts to utmp. > And everything else beyond this is issues with utmp handling. Also $ who ajb85 seat0 2025-07-23 21:17 ajb85 tty1 2025-07-23 21:17 is the wrong output as its not checking for user sessions with sd_session_get_class() - Craig
