I can reproduce it with gdm-3.28-3-20.el8.x86_64

So this is an interesting bug.

For console logins, they get the lock out for "free", because they're just handing off to the shell which is /sbin/nologin.

For graphical logins, we're starting a graphical desktop, not the users shell.

We do still run a shell, however, as part of the login process.  /usr/bin/gnome-session is a shell script that does:

if [ "x$XDG_SESSION_TYPE" = "xwayland" ] &&
   [ "x$XDG_SESSION_CLASS" != "xgreeter" ] &&
   [  -n "$SHELL" ] &&
   grep -q "$SHELL" /etc/shells &&
   ! (echo "$SHELL" | grep -q "false") &&
   ! (echo "$SHELL" | grep -q "nologin"); then
  if [ "$1" != '-l' ]; then
    exec bash -c "exec -l '$SHELL' -c '$0 -l $*'"
  else
    shift
  fi
fi

See it runs exec -l '$SHELL' to execute the users shell as a "login shell" so all the appropriate startup scripts get run.

But also see it explicitly avoids this step for the "nologin" shell. The reasoning for this is discussed upstream here:

https://bugzilla.gnome.org/show_bug.cgi?id=736660#c58

Namely, the login screen itself uses gnome-session and has its shell set to nologin!

But i think we're still safe to remove the check because we also check XDG_SESSION_CLASS to make sure it's not a login screen before proceeding.
In other words, we had redundant checks to skip the script loading for the login screen and dropping one shouldn't hurt anything.

Dropping it, will mean that we try to run nologin as the users shell during login.  it will fail and login will be aborted which is the desired behavior.

devack+

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1766