For the last year or so, there have been regular regressions affecting my integrated AMD gpu, especially with Mesa updates. This includes the most recent update 25.0.6-1 that was pushed to stable by @leigh123linux a few days ago:
The current regression causes constant glitches on my screen, it’s very annoying (AMD-specific debug parameters don’t seem to help).
My main issue is that once these regressions hit me, i’m more or less stuck. When trying to revert the DNF transaction i get errors like this:
$ sudo dnf history undo 372
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
Cannot perform Install action, no match for: mesa-dri-drivers-25.0.4-2.fc42.x86_64.
Cannot perform Install action, no match for: mesa-filesystem-25.0.4-2.fc42.x86_64.
Cannot perform Install action, no match for: mesa-libEGL-25.0.4-2.fc42.x86_64.
Cannot perform Install action, no match for: mesa-libGL-25.0.4-2.fc42.x86_64.
Cannot perform Install action, no match for: mesa-libgbm-25.0.4-2.fc42.x86_64.
Cannot perform Install action, no match for: mesa-va-drivers-freeworld-25.0.4-1.fc42.x86_64.
Cannot perform Install action, no match for: mesa-vdpau-drivers-freeworld-25.0.4-1.fc42.x86_64.
Cannot perform Install action, no match for: mesa-vulkan-drivers-freeworld-25.0.4-1.fc42.x86_64.
Cannot perform Install action, no match for: xdg-desktop-portal-1.20.1-3.fc42.x86_64.
Problem: problem with installed package
- installed package gnome-shell-48.1-1.fc42.x86_64 requires libGLESv2.so.2()(64bit), but none of the providers can be installed
- package gnome-shell-48.1-1.fc42.x86_64 from updates requires libGLESv2.so.2()(64bit), but none of the providers can be installed
- package gnome-shell-48.0-1.fc42.x86_64 from fedora requires libGLESv2.so.2()(64bit), but none of the providers can be installed
- installed package libglvnd-gles-1:1.7.0-7.fc42.x86_64 requires mesa-libEGL(x86-64) >= 13.0.4-1, but none of the providers can be installed
- package libglvnd-gles-1:1.7.0-7.fc42.x86_64 from fedora requires mesa-libEGL(x86-64) >= 13.0.4-1, but none of the providers can be installed
- conflicting requests
You can try to add to command line:
--skip-unavailable to skip unavailable packages
How would i best deal with these situations, without having to wait an unknown period of time before a new Mesa update hits stable?
If it is just Mesa, you not have to undo the whole update, first I would do is, just downgrading the mesa package. In many situations this helped me to avoid the issue mesa brought up.
An alternative wold be to sign up the testing mailing list and try to automate the messages about wayland/mesa issues, so that you already could test und report while it is in testing.
However I tried to get informed about selected topics, unfortunately it is not too intuitive on the mailing list, to get a fast and painless experience.
Unfortunately not enough users, with more complicated Hardware, are making use of the testing process.
It is not needed to follow all the apps wich pass there. Just as in your case testing Wayland and mesa stuff would probably help to test while testing and then you could also down wote the promotion to stable, and reporting the issue, you have to catchend up with a regression, which comes back to stable otherwise.
$ LANG=C sudo dnf downgrade mesa*
Updating and loading repositories:
Repositories loaded.
The lowest available version of the “mesa-libGLU.x86_64” package is already installed, cannot downgrade it.
Total size of inbound packages is 123 MiB. Need to download 123 MiB.
After this operation, 612 KiB will be freed (install 615 MiB, remove 616 MiB).
Is this ok [Y/n]: ^C
