Recently loaded F39 and do updates on Friday evenings. All was good until 15 Dec update. There was no issues with the update until I rebooted. I get the log in screen - enter credentials with no issue, and the desktop starts to load (I get a dark screen and the top menu) but never finishes. When ever I click on something like menu I get thrown back to the login screen. Each login does the same thing. I can ssh to the box with no issues. I can vnc to the box with no issues (everything is normal and works great). I reloaded the OS. Everything works great on the initial install, but when I dnf update - it happens again - constant logout - relogin. I spun up a second test box (same hardware) and it does the exact same thing. I have other F39 boxes with different hardware and they updated fine and are working fine.
I wonder what you have for a GPU in that machine. I have seen several similar issues when an nvidia GPU is used while trying to use the default nouveau drivers.
If you have an nvidia gpu with the nvidia drivers it is also possible that the drivers may not have been properly updated when the upgrade occurred on the 15th.
If you already have the nvidia drivers and this is happening the fix is usually very easy.
I’m seeing the same issue. Going back to earlier kernels doesn’t seem to work. Saw another thread about downgrading the mutter version but haven’t gotten this to work.
It seems like anytime I press the “super” key, I am booted out of my session.
If I open more than one program from my task bar, I get booted out
This thing is pretty old (i5 with a Windoz Vista sticker). I have heard stories about nvidia and Fedora. This thing has the built in:
Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
Intel Q45/Q43(ELK)
I also have started with a fresh load of F39 on a similar machine and after the initial install did a normal update and it craps out after the reboot. I will try the remove command on the test box I stood up tonight.
Similar issues (login gives dark screen or GUI crashes and sends you back to the login screen, but system still responds to ssh) were reported by several Fedora users on Reddit so this looks like a bug that affects multiple users. This is not the first time changes to current software inadvertently break things for people using older hardware – developers don’t normally use old hardware, and vendors may not support it with firmware updates.
Anyone experiencing the issue should check that the kernel is still alive by logging in from another system with ssh and then post hardware details (sudo inxi -Fzxx) or upload a [LHDB probe] (https://linux-hardware.org) (sudo -E hw-probe -all -upload) and post the link. journalctl should have some helpful details if you make the effort to find them among the mass of messages unrelated to your issue.
Some news on my side: I updated my F39 installation this morning using the terminal (ctrl alt F3) on my old Thinkpad X200 and rebooted. I saw some mesa packages being updated and that gave me hope for a possible fix. I can now log on graphically to GNOME wayland and everything seems fine at first glance. I can also open applications like gnome-terminal and firefox without any issues. However, some applications such as nautilus and gnome-software still have some visual artifacts.
FWIW, I have not seen these issues on my latest Thinkpad (current daily driver).
You may get useful data by comparing journalctl records for the latest boot with one that was looping to the login screen. This will, however, need work to find the right search terms.
You can make the inix output more readable by selecting the text and using the </> button, or byjust adding triple backquote (```) lines before and after the inxi output. Remember that forum posts are searchable and form a record that often helps others who encounter the same problem.
You aren’t using Xorg – Xwayland just translates Xorg to Wayland (and loses certain things in translation due to fundamental differences like cross-window connections – to can see the difference try usiing xeyes).
The latest update to Mesa this morning fixed all the remaining graphical artifact issues that had been plaguing my Thinkpad X200 setup with vanilla F39 for a few days.