Bug 2467281

Summary: Push mesa-26.0.6-2.fc44 to stable
Product: [Fedora] Fedora Reporter: Yi Hao <leongyihao>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 44CC: ajanulgu, ajax, asrivats, fedora, igor.raits, janne-fdr, jexposit, j, lyude, marcandre.lureau, mpenttil, philip.wyett, rstrode, suraj.ghimire7, tstellar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-05-08 06:57:06 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:

Description Yi Hao 2026-05-06 16:38:42 UTC 
RPM Fusion already pushed it to the update, causing rebase in Silverblue to fail.
dnf upgrade inside toolbox fail for the same reason

Reproducible: Couldn't Reproduce

Steps to Reproduce:
dnf upgrade with rpmfusion repo
Actual Results:
rpmfusion only contains version 26.0.3 and 26.0.6

Expected Results:
Atomic variant successfully rebase. 
dnf upgrade success
Comment 1 José Expósito 2026-05-07 07:54:24 UTC 
Hi!

A user reported a regression in mesa v26.0.6:
https://bodhi.fedoraproject.org/updates/FEDORA-2026-0eac96c261#comment-4638422

I requested feedback to understand how often the bug happens. I'm in a lose-lose situation where pushing the build will affect some users but not pushing it is affecting RPM users.

I'll wait for the affected user's feedback a bit longer and ask some people in the meantime to find the best possible solution.
Comment 2 José Expósito 2026-05-08 06:57:06 UTC 
After speaking with some mesa developers, I pushed mesa v26.0.6. For additional context: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0eac96c261#comment-4639228