[neon/neon-packaging/plasma-login-manager/Neon/stable] debian: sync pam to ubuntu

[Carlos De Maine]

Git commit bd8d1be173ae24bdabb967cfffd1acb9f88a0d11 by Carlos De Maine.
Committed on 16/06/2026 at 05:12.
Pushed by carlosdem into branch 'Neon/stable'.

sync pam to ubuntu

M  +4    -0    debian/plasmalogin.pam
M  +3    -0    debian/plasmalogin.plasmalogin-autologin.pam
M  +3    -0    debian/plasmalogin.plasmalogin-greeter.pam

https://invent.kde.org/neon/neon-packaging/plasma-login-manager/-/commit/bd8d1be173ae24bdabb967cfffd1acb9f88a0d11

diff --git a/debian/plasmalogin.pam b/debian/plasmalogin.pam
index de7fd79..172b78d 100644
--- a/debian/plasmalogin.pam
+++ b/debian/plasmalogin.pam
@@ -6,6 +6,7 @@ auth    required        pam_succeed_if.so user != root quiet_success
 
 # auth    sufficient      pam_succeed_if.so user ingroup nopasswdlogin
 @include common-auth
+
 # gnome_keyring breaks QProcess
 -auth   optional        pam_gnome_keyring.so
 -auth   optional        pam_kwallet5.so
@@ -16,11 +17,14 @@ auth    required        pam_succeed_if.so user != root quiet_success
 # lingering context has been cleared.  Without this it is possible that a
 # module could execute code in the wrong domain.
 session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
+
 # Create a new session keyring.
 session optional        pam_keyinit.so force revoke
 session required        pam_limits.so
 session required        pam_loginuid.so
+
 @include common-session
+
 # SELinux needs to intervene at login time to ensure that the process starts
 # in the proper default security context.  Only sessions which are intended
 # to run in the user's context should be run after this.
diff --git a/debian/plasmalogin.plasmalogin-autologin.pam b/debian/plasmalogin.plasmalogin-autologin.pam
index d595682..b24b876 100644
--- a/debian/plasmalogin.plasmalogin-autologin.pam
+++ b/debian/plasmalogin.plasmalogin-autologin.pam
@@ -10,11 +10,14 @@ auth    required        pam_permit.so
 # lingering context has been cleared.  Without this it is possible that a
 # module could execute code in the wrong domain.
 session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
+
 # Create a new session keyring.
 session optional        pam_keyinit.so force revoke
 session required        pam_limits.so
 session required        pam_loginuid.so
+
 @include common-session
+
 # SELinux needs to intervene at login time to ensure that the process starts
 # in the proper default security context.  Only sessions which are intended
 # to run in the user's context should be run after this.
diff --git a/debian/plasmalogin.plasmalogin-greeter.pam b/debian/plasmalogin.plasmalogin-greeter.pam
index 78aed41..5b65a1d 100644
--- a/debian/plasmalogin.plasmalogin-greeter.pam
+++ b/debian/plasmalogin.plasmalogin-greeter.pam
@@ -8,11 +8,14 @@ auth    required        pam_permit.so
 # lingering context has been cleared.  Without this it is possible that a
 # module could execute code in the wrong domain.
 session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
+
 # Create a new session keyring.
 session optional        pam_keyinit.so force revoke
 session required        pam_limits.so
 session required        pam_loginuid.so
+
 @include common-session
+
 # SELinux needs to intervene at login time to ensure that the process starts
 # in the proper default security context.  Only sessions which are intended
 # to run in the user's context should be run after this.