UPDATE: I checked the logs & found a few relevant entries. But it basically says that for some reason it cant initialise OpenGL backend, then stops wayland followed by all Qt processes failing causing any GUI elements to completely fail after that. What should i do now? I can't use dnf since the wifi isnt connected yet in the tty3 so should I try a repair from the live boot?
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Are you using the rpm-fusion mesa drivers or Fedora's (assuming you use Intel / AMD card)?
You can connect to wifi via tty using nmcli command: nmcli --ask dev wifi connect CoolNetwork123
Or you can use nmtui if you prefer a graphical frontend
alongside Windows 11 23H2
Wasn't there news of a Windows update breaking dual booting recently? Could be that?
Yeah but that broke GRUB and had a pretty specific error message associated with it. I don't think problems with grub look like what OP is describing (although I don't know enough to say for sure).
Anecdotally, I'm running a Fedora Atomic-based OS alongside Windows and that Windows update didn't cause any problems for me.
Boot off the live boot disk and, after mounting everything, chroot into your Fedora install. Then try rebuilding your initramfs (I don't know the command for Fedora, but I'm sure it's simple enough).
Switch to a different tty console, login, and see what the logs say.
I know I can press esc to check the startup logs, which might hive a few more details. But I'm out right now, so I can't check till later.
That's not what I mean. You can just switch to a different tty console. Your default on boot is a graphical interface, but there are others ready and available.
https://www.dhiller.de/2020/02/13/switch-to-console-on-fedora.html
Oh, I hadn't realised those were there. I'll see if I can get the GUI back up through the terminal. Do you have any idea what might've causes it to fail in the first place, though?
Could be anything. Driver issues, memory issues, config issues..who knows.
Just check logs once you get logged in, and it should be easier to figure out.
No disk space available, corrupt startup scripts, borked update, etc...