On 18.08.2024 11:15, Andrei Borzenkov wrote:
On 18.08.2024 10:43, David C. Rankin wrote:
On 8/18/24 2:25 AM, Andrei Borzenkov wrote:
Does kdm3 support systemd-logind at all? Do you have other systems with kdm3 and pre-systemd 256? What is output of loginctl there?
I seriously doubt kdm3 supports systemd-logind, but it works fine. On 15.4 there is no "manager" login -- which makes sense given what you said earlier.
Booting to 15.4 instead of Tumbleweed I get:
$ loginctl list-sessions --no-legend 2 1000 david seat0
So, there is no change. Looking at susepaste source, it does not use TTY field at all, so the obvious fix is to ignore session of type "manager". If it results in more than one real user session, it had been always broken already.
Now, if the intent is to make it work for multiple user sessions ... there is apparently undocumented session ID argument "auto" which magically shows you your current session.
Sorry, lost the command invocation bor@bor-Latitude-E5450:~$ loginctl show-session auto
Id=1 User=1001 Name=bor Timestamp=Sun 2024-08-18 07:38:13 MSK TimestampMonotonic=62977112 VTNr=2 Seat=seat0 TTY=tty2 Remote=no Service=gdm-autologin Scope=session-1.scope Leader=1442 Audit=1 Type=wayland Class=user Active=yes State=active IdleHint=no IdleSinceHint=1723965638090394 IdleSinceHintMonotonic=9807885579 LockedHint=no bor@bor-Latitude-E5450:~$
So, no "loginctl --list-sessions" needed at all. It was added in v243. Leap 15.5 has v249. Do not have 15.4 anymore, but susepaste can fallback to the current code if systemd version is older.