Unsure how much this issue is Asahi-related or not. I reinstalled Asahi after a while with KDE. I then installed sway and niri (via Dank Material Shell) with the intention of trying out both. I then logged out of KDE and ended up with a dark screen. Whenever I restart, the screen is dark after the boot sequence until I press the power button once (after which the screen shows the Fedora shutting down sequence).
I do still see the U-boot stuff and can get into the GRUB menu, but I’m unsure how exactly I can repair Fedora. When going into GRUB, only one Fedora Linux option (as well as a UEFI boot) both show up.
Let me know how I can collect more info to help troubleshoot, thanks!
Can you switch to a TTY and log in with your username & password in text mode?
If no, can you try booting from a USB device and analyze the system logs as described here?
There should be something around the time when you try to log in.
Also, you could use dnf history list, dnf history info to identify which of the last dnf transactions was causing the problem, then use dnf history undo <number> to undo that transaction(s).
Logged into TTY, tried to start plasmadesktop and it didn’t work. Ran systemctl –user restart plasma-plasmashell.service, which didn’t work, so I checked the logs via journalctl --user -xeu plasma-plasmashell.service. Logs showed that there was no display to connect to, and that $WAYLAND_DISPLAY and $DISPLAY weren’t set, and KWin crashed before plasmashell started. (Shoutout Claude for interpreting my logs lol, maybe it wasn’t fully correct but it did work so)
After running systemctl on kwin_wayland.service, I saw that it was crashing on startup because of a mismatched symbol in the KDecoration library (_ZN12KDecoration3120borderOutlineChangedEv) (once again, shoutout Claude).
I updated KWin to match KDecoration, and I ran “distro sync.” I’m unsure which of those did it, but after restarting, it worked.