Bug 2357471
Summary: | Update mesa to 25.0.3 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Rusek <drusek> |
Component: | mesa | Assignee: | ajanulgu |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 42 | CC: | ajax, awilliam, bskeggs, igor.raits, jexposit, j, kparal, lbrabec, lruzicka, lyude, mail, marcandre.lureau, ndegraef, rstrode, suraj.ghimire7, tstellar, walter.pete |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | mesa-25.0.3-2.fc41 mesa-25.0.4-2.fc42 | Doc Type: | --- |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2025-04-13 01:39:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2291266 |
Description
Daniel Rusek
2025-04-04 10:14:10 UTC
Proposed as a Freeze Exception for 42-final by Fedora user asciiwolf using the blocker tracking app because: Mesa 25.0.3 contains many bug fixes for visual glitches and other bugs/regressions present in previous 25.0.x releases. +6 in https://pagure.io/fedora-qa/blocker-review/issue/1836 , marking accepted FE. FEDORA-2025-a6cb1a1aaa (mesa-25.0.3-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-a6cb1a1aaa FEDORA-2025-53bc6e20bf (mesa-25.0.3-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-53bc6e20bf Changing back to a proposed FE due to discovered issues: https://pagure.io/fedora-qa/blocker-review/issue/1836#comment-964577 Discussed during the 2025-04-07 blocker review meeting [1]: * AGREED: 2357471 - punt - We'll wait until the regression is fixed, and then consider it again (if there's still time). [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-04-07/f42-blocker-review.2025-04-07-16.01.log.html FEDORA-2025-53bc6e20bf has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-53bc6e20bf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-53bc6e20bf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-a6cb1a1aaa has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a6cb1a1aaa` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a6cb1a1aaa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I have updated Mesa to 25.0.3 and have not noticed any problems so far. We're waiting for this issue to get fixed: https://pagure.io/fedora-qa/blocker-review/issue/1836#comment-964826 https://github.com/rhinstaller/anaconda/pull/6339 FEDORA-2025-a6cb1a1aaa (mesa-25.0.3-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-47e9ecf4a6 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-47e9ecf4a6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-47e9ecf4a6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-47e9ecf4a6 (mesa-25.0.4-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |