Login error after update

Ask Fedora
1

I updated my fedora to 44 and gnome KDE secure-something (2011->2023) [can’t remember it’s exact name] yesterday. Currently, when I write my password it sends me back to user selection screen. When I write a wrong password it says “password authentication didn’t work”. I also tried GNOME classic instead of Gnome in password screan but nothing changed. I tried to login via tty screen via ctrl+alt+F3 but it says “Login incorrect”. I tried to run the fedora 43 from grub screan but it also has the same issue so I think the issue is due to gnome update. I started the computer in rescue mod and it showed me some error messages, I’m adding the images below.
I checked other posts and saw it’s mostly due to nvidia drivers but I don’t even have GPU, yet alone nvidia drivers.
Thanks in advance.

IMG_20260502_091714
IMG_20260502_0917141920×1440 455 KB

IMG_20260502_091728
IMG_20260502_0917281920×1440 479 KB

IMG_20260502_092040
IMG_20260502_0920401920×1440 293 KB

2

This might be a long shot, but does it work if you boot with the enforcing=0 boot flag (by editing the GRUB menu entry), which would temporarily set SELinux to permissive mode?

If it’s working, then you could restore the SELinux contexts, e.g. by rebooting and using the autorelabel=1 boot flag at the GRUB menu for the selected entry.

3

Issue resolved by Gemini, the explanation below also belongs to gemini.

The problem occurred in two stages:

  1. The system dropped into Emergency Mode due to a filesystem error (dirty bit) on the /boot/efi partition. This was resolved by running fsck.vfat from the TTY to repair the partition.
  2. After normal boot resumed, the system was stuck in a login loop. This was caused by corrupted GNOME desktop configuration files in the user profile conflicting with the system.

The Solution: I switched to a TTY interface and renamed the user configuration folders (~/.config, ~/.local, and ~/.cache to .bak). This forced the desktop environment to generate fresh, default settings upon the next login. Once logged in successfully, I selectively copied back only the configuration files for third-party applications from the backups, making sure to exclude GNOME system configs (like dconf, mutter, gnome-shell, etc.) to prevent the loop from returning.