Hi, I have upgraded today to Fedora 41,but in the Gnome login screen, I select my user, enter password and takes me back to the screen again to select the user. I have tried all the options in the gear icon: classic, classic in Xorg,… None of them work. After logging in via terminal and entering “startx” I can access to the desktop. I have disabled all Gnome extensions, and restart. This doesn’t work either. Then I have created a new user, and I can’t login with the new user either. It happens the same when I enter the password, it takes me back to the user selection screen again.
Fedora 40 was running smoothly with no issues. My laptop is a Lenovo X1 Carbon 7th gen.
I have uploaded to Imgur a screenshot of the journal where I think the issue could be. I cannot upload it to the forum because it seems that Nautilus does not open up to select files. Maybe because I launched the desktop with “startx” from the terminal.
I’m having similar issue, where I cannot login into the system from Gnome but not from the terminal either after upgrading to 41 from 40. Double checked my credentials, they’re correct.
I did not know that there are more users affected. I was yesterday for hours looking for a solution, reading a lot of forums and websites, and I did not read about anyone else with this issue.
I hope they find the cause and provide a fix soon.
Can you at least login via tty?
I had the same problem, was getting the error about root partition having no space. I ran btrfs balance start -dusage=5 / and that seemed to solve the issue.
Thanks Andrzej! I have solved it in a different way, but it seems the issue was related to what you have shared.
It seems that Snapper had many snapshots and I had only about 5-6 Gb free (i did not know about this at first). So the upgrade had some issues during the process although I managed to complete it. But then I was facing the login issue.
What I did is rollback to a snapshot prior the upgrade, I deleted many old snapshots until I got around 45 Gb of free space, and then I initiated the upgrade process again. After completing the upgrade now everything works like a charm.
I did not know that snapper had used a lot of space and almost filled the whole partition although I have the cleanup job enabled. I will pay more attention to this from now on.
I have a similar problem. I just upgraded a KDE spin in a VM from 40 to 41. The upgrade process seemed to stall at 89% for several minutes, then the upgrade completed very quickly and the VM rebooted. After reboot, attempting to log in as an ordinary user or as root either on a tty or via the gui results in immediately returning to the login prompt. Is there some way that I can log in to take a look at the disk partitions etc?
Same thing just happened to me. Perpetual recycling. When I clicked setting on the bottom right of the login screen and switched from gnome to gnome Xorg, I was then able to login. Now I’m scared to reboot or shutdown.
I realized that in Fedora 40, I set “WaylandEnable=false” in /etc/gdm/custom.conf, which was causing this issue in Fedora 41, after the upgrade. As in Fedora 41, Gnome X11 sessions are dropped and Wayland has to be enabled by default, I had to comment this line to allow Wayland to work as expected in Fedora 41:
I installed gnome-session-xsession on F41, tried selecing GNOME on X from log-in, and got the log-in loop.
Wayland logs-in fine so that has me figure that GNOME on X isn’t hooked-up properly on F41, and assume any upgrades from F40 → F41 where GNOME on X is used or forced via custom.conf will likely also not work.
I know Fedora is pushing Wayland, but presume it’s a bug for Xorg sessions to still be offered with the gnome-session-xsession package and it not just-work.
I found and fixed the problem. I have an old version of the zscaler client installed on that VM. The zscaler client adds to the selinux policy but the syntax used in the old zscaler client isn’t compatible with the current selinux software. It comprehensively blew up selinux leaving bash (& pretty much everything else) inaccessible. I added ‘selinux=0’ to the end of the linux line in the grub menu; that allowed linux to start with no selinux then I could log in and sort out the problem with the client software.