Hallo Dev,
I’ve installed and upgraded (6.12.9) only to see the distro is hung!
I can’t even boot into the default kernel (6.11.4) either.
Do I have to delete the VM and create new one or?
Hallo Dev,
I’ve installed and upgraded (6.12.9) only to see the distro is hung!
I can’t even boot into the default kernel (6.11.4) either.
Do I have to delete the VM and create new one or?
Hi and welcome to !
You might be affected by the updated mesa
affecting VMWare and Virtualbox machines. See here for details and temporary fix. You might need to log into a tty console in order to perform the mesa downgrade, given that you can’t log into a graphical session.
Thank you very much.
I’m wondering why is this issue still exists given the fact that FC41 is several months old.
Anyway, I’ll create a new VM and see what happens after the complete upgrade of the new OS.
From what I’ve seen, this is a regression bug introduced by mesa
a few months after F41 was released.
A new VM will probably suffer from the same issue after a dnf upgrade
, given that mesa will be upgraded along.
Easiest workaround would be to log into a text console from your existing VM (by pressing Ctrl+Alt+F3
or Ctrl+Alt+F2
, then run:
sudo dnf downgrade mesa*
Afterwords you can lock the downgraded versions of mesa
packages with the below command, until the issue gets fixed:
echo "excludepkgs=mesa*" | sudo tee -a /etc/dnf/dnf.conf > /dev/null
VMware and VirtualBox are third-party tools known to suffer from this kind of issues.
It works fine using libvirt+KVM/QEMU as well as bare metal, so consider these options.
I tried to specifically investigate which package update is the reason for this. my result is in sync with your idea, is caused by mesa
packages.
I have now used your line of code to lock the version, however can i know how to unlock the version when is needed?
When the issue gets fixed and the updated packages are known to have landed in the repos, you can delete (or comment out) the line added in the /etc/dnf/dnf.conf
file.
Guten Tag!
Unfortunately I’ve deleted that VM and using another VM (41 Cinnamon) now.
Now, I’m stuck here too – sunai is not in the sudoers file.
I’ve followed the file as described here:
%wheel ALL=(ALL) ALL
That entry is already uncommented (visudo) so what else should I do to make sudo work?
Thanks for your responses though.
[sudo] password for sunai:
Updating and loading repositories:
Copr repo for PyCharm owned by phracek 100% | 6.4 KiB/s | 4.5 KiB | 00m01s
Fedora 41 openh264 (From Cisco) - x86_64 100% | 6.2 KiB/s | 6.0 KiB | 00m01s
Fedora 41 - x86_64 - Updates 100% | 1.9 MiB/s | 8.6 MiB | 00m05s
RPM Fusion for Fedora 41 - Nonfree - Steam 100% | 6.9 KiB/s | 21.7 KiB | 00m03s
RPM Fusion for Fedora 41 - Nonfree - NVIDIA Driver 100% | 14.1 KiB/s | 26.2 KiB | 00m02s
Fedora 41 - x86_64 100% | 2.8 MiB/s | 35.4 MiB | 00m13s
google-chrome 100% | 10.4 KiB/s | 3.2 KiB | 00m00s
Repositories loaded.
The lowest available version of the “mesa-dri-drivers.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-filesystem.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-libEGL.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-libGL.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-libGLU.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-libgbm.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-libglapi.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-va-drivers.x86_64” package is already installed, cannot downgrade it.
The lowest available version of the “mesa-vulkan-drivers.x86_64” package is already installed, cannot downgrade it.
Nothing to do.
sunai@vbox:~$ echo “excludepkgs=mesa*” | sudo tee -a /etc/dnf/dnf.conf > /dev/null
I’m going to do the system update and see what happens next…
sudo dnf -y update
Then reboot – now I can’t find the login screen!
What’s going on here?
41LxDE distro has no such issue – I can login after the downgrade and full system update.
The issue is with 41WS distro.
This is probably because you ran the command on an F41 fresh install, hence there was nothing to downgrade. The downgrade should be performed when on a mesa
version with issues.
I would advise against using the -y
flag, in order to be able to catch what is being upgraded, and cancel the procedure if necessary. It’s possible that something went wrong with excludepkgs
option added to /etc/dnf/dnf.conf
, and the mesa
pachages have been upgraded.
You can try to reach a text console, log in, and from there run the sudo dnf downgrade mesa*
command.
If it works, and now you can access a graphical session, you can check the contents of /etc/dnf/dnf.conf
. Please post here the output.
Please also run dnf history list
to check the previous dnf
commands, then run dnf history info <transaction-id> | grep mesa
[1] and post here the output as well.
When posting terminal outputs, please mark the corresponding text as preformatted text using the </>
button, after having highlighted the text.
Replacing with the actual id of the dnf transaction including the last upgrade. ↩︎