Upgrading Fedora on my home desktop PC last night was a bit more exciting than usual. It's a bit of a Ship of Theseus PC and has gone through several hardware upgrades and many, many incremental distro upgrades since the last clean install, which appears to have been Fedora 31 from way back in 2019. These upgrades have generally gone smoothly, but after running the upgrade from Fedora 42 to 43 I was left with a computer where GDM would crash on startup, leaving me with an unresponsive black screen instead of a login prompt.
Fortunately a bit of searching led me to the root cause and the fix, and I was able to SSH in and get the machine working again. It's a bit of a corner case that only affects machines that were originally running Fedora 35 or older, and somehow missed the migration to authselect that should have happened automatically when upgrading to Fedora 36: https://discussion.fedoraproject.org/t/gdm-crashes-after-upgrade-to-fedora-43-due-to-authselect-migration/171961

GDM crashes after upgrade to Fedora 43 due to authselect migration
Problem Some systems are experiencing GDM crashes, resulting in the desktop failing to load and the system becoming unusable (no console access, blank display) with the relevant error logged in journalctl: gdm-launch-environment][1722]: PAM unable to dlopen(/usr/lib64/security/pam_lastlog.so): Stack trace of thread 1701: ...snip... username systemd[1]: systemd[1]: systemd-coredump: Deactivated successfully. Cause The GDM crash is caused by the system using an old configuration (non-authselect,...
