Description of problem: pam_krb5.so seems to be missing after upgrade to Fedora 35, but files in pam.d still reference it. As a result, gdm will not start. Version-Release number of selected component (if applicable): 1.5.2-5 How reproducible: Steps to Reproduce: 1. Upgrade from Fedora 34 to Fedora 35 using dnf system-upgrade Actual results: After upgrade, system boots to a blank screen with a cursor Expected results: System should start normally after upgrade and boot to gdm login screen Additional info:
Thanks for the bug report. I highly doubt this is due to `pam_krb5` missing, as that module has been retired since at least Fedora 32. Did you verify your system configuration has been updated after the update? $sudo rpmconf -a
You're right, it wa(In reply to Björn 'besser82' Esser from comment #1) > > I highly doubt this is due to `pam_krb5` missing, as that module has been > retired since at least Fedora 32. You're right, it wasn't. I thought PAM was to blame for gdm not starting because the most noticeable error messages in the output from `journalctl -xe -u gdm` were those about the inability to load pam_krb5.so. But on further investigation I found that the actual reason gdm didn't start was that `dnf system-upgrade` had run out of disk space and failed to remove a bunch of F34 packages. I've reported this separately in #2021590. > Did you verify your system configuration has been updated after the update? > $sudo rpmconf -a No, but I manually copied the .rpmnew files in /etc/pam.d over top of the existing config files, and I no longer see the log messages about pam_krb5.so.