etc/pam.d/login: Register sessions with systemd-logind #599
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AI disclaimer: This merge/pull request was generated by claude-opus-5.5 and reviewed by Paul Menzel (@pmenzel).
Commit 2c83b58 (etc/pam.d: Remove obsolete pam_ck_connector (ConsoleKit)) removed the ConsoleKit connector without adding its successor
pam_systemd. So a console login on a virtual terminal is not registered with systemd-logind: it gets no session, no seat, and no device ACLs. Compositors using libseat (for example sway) therefore cannot open the DRM and input devices, when started from the console.Add
pam_systemdas optional session module afterpam_loginuid, like already done inetc/pam.d/sshd,etc/pam.d/system-auth, andetc/pam.d/lightdm.Tested on maleficent with:
loginctl session-statuson a VT login showsSeat: seat0.