-
Notifications
You must be signed in to change notification settings - Fork 114
Description
Arch Linux
linux 6.18.5.arch1-1
systemd 259-2
kmscon-git 2:v9.2.1.r75.g0aaa927-1
util-linux 2.41.3-2
pambase 20250719-1
Starting kmscon from systemd with an updated unit service file largely copied from the current getty@.service, but with the usual other bits from kmsconvt@.service, and running pam_systemd.so with debug:
ExecStart=/usr/bin/kmscon --vt=%i --seats=seat0 --no-switchvt --login -- /usr/bin/agetty --noreset --noclear - ${TERM}
Upon login, kmscon starts normally, but pam_systemd throws an error,
pam_systemd(login:session): Asking logind to create session: uid=1000 pid=70677 service=login type=tty class=user desktop= seat=seat0 vtnr=0 tty=pts/14 display= remote=no remote_user= remote_host=
systemd[1]: varlink-50-50: Changing state pending-disconnect → processing-disconnect
login[70677]: pam_systemd(login:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a
systemd[1]: varlink-50-50: Changing state processing-disconnect → disconnected
login[66874]: pam_systemd(login:session): Varlink call io.systemd.Login.CreateSession failed: org.varlink.service.InvalidParameter
Running the stock kmsconvt@.service did the same thing. Running kmscon manually does the same thing.
Importantly, failing to create a new session, not all environment variables are set properly, particularly XDG_RUNTIME_DIR=.
Of course, without proper session initialization, userspace kmscon cannot be used in place of, or overlaying, kernelspace fbcon.
Any thoughts?