Upstream have proposed a fix:
https://gitlab.gnome.org/GNOME/gdm/merge_requests/20
Please test it when you can.
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Description changed:
+ https://gitlab.gnome.org/GNOME/gdm/issues/399
+
+ ---
+
In case of the following scenario:
1. PAM configured to run auth and session with pam_exec scripts synchronizing
via SIGUSR1
2. Using GDM as the login manager causes SIGUSR1 never reaches the target
scripts.
Workaround:
a) Use SIGUSR2 in the scripts.
b) Comment out block_sigusr1() call in daemon/main.c.
To reproduce add the following entries:
/etc/pam.d/common-auth:
auth optional pam_exec.so log=/tmp/auth.log expose_authtok quiet
/usr/local/bin/auth.py
/etc/pam.d/common-session:
session optional pam_exec.so log=/tmp/session.log
/usr/local/bin/session.py
Attaching example scripts.
When using SIGUSR1 - sigusr1_handler is never called, with SIGUSR2 it is
called without issues.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1782152
Title:
GDM blocks SIGUSR1 used in PAM scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
