Bug 2457852

Summary:	Enable AMD Anti-Lag layer in Vulkan build configuration
Product:	[Fedora] Fedora	Reporter:	theinsanegamer23
Component:	mesa	Assignee:	Adam Jackson <ajax>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	43	CC:	agurenko, ajanulgu, ajax, asrivats, cfnptr, development.group, fedora, igor.raits, janne-fdr, jexposit, j, lyude, marcandre.lureau, mpenttil, rstrode, suraj.ghimire7, tstellar
Target Milestone:	---	Keywords:	RFE
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	mesa-26.2.2-6.fc45	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-09-07 06:44:56 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 theinsanegamer23 2026-04-13 14:55:52 UTC

It appears that the Fedora mesa package is currently built without the AMD Anti-Lag Vulkan layer enabled. This feature is increasingly important for latency reduction in gaming on RDNA-based hardware.

The layer is currently missing from the vulkan-layers definition in the .spec file, which prevents users from utilizing AMD_anti_lag functionality even when using compatible hardware and drivers.

Reproducible: Always

Steps to Reproduce:
1. Install mesa-vulkan-drivers.

2. Check available Vulkan layers using vulkaninfo --summary.

3. Observe that the AMD Anti-Lag layer is not present in the output.
Actual Results:
AMD Anti-Lag is not an included Vulkan layer.

Expected Results:
AMD Anti-Lag should be an included Vulkan layer.

Comment 1 cfnptr 2026-07-15 11:52:22 UTC

Sounds like a very easy fix, can we increase severity for this?

Comment 2 theinsanegamer23 2026-08-31 01:13:26 UTC

Increased severity of the bug report, as suggested above.

Comment 3 José Expósito 2026-09-07 06:44:56 UTC

Enabled in Fedora Rawhide and Fedora 45:
https://src.fedoraproject.org/rpms/mesa/pull-request/165

Comment 4 Fedora Update System 2026-09-07 08:17:06 UTC

FEDORA-2026-fed9f8b547 (mesa-26.2.2-4.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-fed9f8b547

Comment 5 Fedora Update System 2026-09-08 01:36:56 UTC

FEDORA-2026-fed9f8b547 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-fed9f8b547`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-fed9f8b547

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-09-11 01:35:40 UTC

FEDORA-2026-06a5023802 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-06a5023802`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-06a5023802

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-09-12 01:43:51 UTC

FEDORA-2026-06a5023802 has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-06a5023802`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-06a5023802

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-09-17 00:17:54 UTC

FEDORA-2026-06a5023802 (american-fuzzy-lop-5.03c-2.20260904gitbcd3b65.fc45, clazy-1.17-4.fc45, and 7 more) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.