Talk: GDM crashes after upgrade to Fedora 43 due to authselect migration

Ask Fedora
1

This is a discussion topic for the following Common Issue:

You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.

If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.

3 Likes
GDM crashes after upgrade to Fedora 43 due to authselect migration
2

Please see the Common Issue for solution/workarounds:

3

I followed an earlier work around suggested somewhere that involved editing /etc/shadow. Do I need to revert that change before applying the steps mentioned here?

Thanks again for the update on this issue.

4

/etc/shadow stores your passwords for root or users locally. If you did any changes to /etc/shadow I recommend you to revert.

1 Like
5

I think this is exactly the same issue as I have already reported here:

Should I have created that as common issue right away?

6

It’s good to file a bug report, and you can propose an issue like this one as a common issue, or ideally document it yourself in Common Issues > Proposed Common Issues , yes. Especially if it has a high impact, or affects a large number of users.

7

Hello everyone,

I just registered and came here to say that I experienced the issue when upgrading from F41->F43 (a bit late I know :wink:).
In my case, the issue was compounded by the fact that:

  • the root account is locked by default, hence a non-graphical boot + emergency prompt that is non-functional :sob:
  • I then attempted to restore the root account
    • the official doc instructions seem outdated: after changing the root account password and rebooting, the new password would not be accepted (‘invalid password’) at the next system boot.
    • more searches brought in potential SELinux issues but despite following these steps to reset the root password, they did not work either (same ‘invalid password’ error).
  • furthermore, after these steps, I found and followed your workaround to boot into multi-user, non-graphical system but this time, the password for my normal user would not be accepted (again 'invalid password)
  • at this point, I was about to resort to reinstalling while keeping my home directory but found that the installer would error out because of my /boot partition being too small.
    • I have indeed been updating my system from at least F33 from I see in my notes (probably earlier) so I have a 500 MiB /boot partition (it looks like I could probably have used the ‘mount point assignment’ option instead though).
  • after much searching, I realized the issue came from the previous steps touching /etc/shadow but not properly relabeling it SELinux-wise. After calling restorecon on the file, my local user password was enventually accepted at the next boot and I could use the workaround to fix the authselect issue.

So thank you for documenting the issue and its workaround :folded_hands: ! It looks like I have some maintenance tasks on my side to adjust to the new system requirements after system-upgrade’ing for so long :slightly_smiling_face: but this was quite distressful. Hopefully, others can find this post too and this is useful :crossed_fingers: