After a lot of experimentation, I have some interesting news.
For me, uninstalling pam_pkcs11 makes the issue go away, even when using the latest “broken” pam version 1.6.1-4.1.
Can anyone confirm this?
Edit: Don’t forget locking pam_pkcs11 after uninstalling, i.e. with sudo zypper addlock pam_pkcs11
, or else it will be auto-reinstalled with the next update!
Just a quick update:
Fabain Vogt managed to identify the exact problem over on bugzilla.
With that information I was able to make a patch and submitted that:
If all goes well and I didn’t screw up anything in the sumbit request, an official patch for pam_pkcs11 should be available in a few days.