1### Before submitting your bug report: 2- Check if a new version of Mesa is available which might have fixed the problem. 3- If you can, check if the latest development version (git main) works better. 4- Check if your bug has already been reported here. 5- For any logs, backtraces, etc - use [code blocks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks), GitLab removes line breaks without this. 6 - Do not paste long logs directly into the description. Use https://gitlab.freedesktop.org/-/snippets/new, attachments, or a pastebin with a long expiration instead. 7- As examples of good bug reports you may review one of these - #2598, #2615, #2608 8 9 10Otherwise, fill the requested information below. 11And please remove anything that doesn't apply to keep things readable :) 12 13 14The title should effectively distinguish this bug report from others and be specific to issue you encounter. When writing the title of the bug report, include a short description of the issue, the hardware/driver(s) affected and application(s) affected. 15 16 17### Description 18 19Describe what you are doing, what you expect and what you're 20seeing instead. How frequent is the issue? Is it a one time occurrence? Does it appear multiple times but randomly? Can you easily reproduce it? 21 22"It doesn't work" usually is not a helpful description of an issue. 23The more detail about how things are going wrong, the better. 24 25### Screenshots/video files 26 27For rendering errors, attach screenshots of the problem and (if possible) of how it should look. For freezes, it may be useful to provide a screenshot of the affected game scene. Prefer screenshots over videos. 28 29### Log files (for system lockups / game freezes / crashes) 30 31- Backtrace (for crashes) 32- Output of `dmesg` 33- Hang reports: Run with `RADV_DEBUG=hang` and attach the files created in `$HOME/radv_dumps_*/` 34 35### Steps to reproduce 36 37How can Mesa developers reproduce the issue? When reporting a game issue, start explaining from a fresh save file and don't assume prior knowledge of the game's story. 38 39Example: 40 411. `Start new game and enter second mission (takes about 10 minutes)` 422. `Talk to the NPC called "Frank"` 433. `Observe flickering on Frank's body` 44 45### System information 46 47Please post `inxi -GSC -xx` output ([fenced with triple backticks](https://docs.gitlab.com/ee/user/markdown.html#code-spans-and-blocks)) OR fill information below manually 48 49 50- OS: (`cat /etc/os-release | grep "NAME"`) 51- GPU: (`lspci -nn | grep VGA` or `lshw -C display -numeric`) 52- Kernel version: (`uname -a`) 53- Mesa version: (`glxinfo -B | grep "OpenGL version string"`) 54- Desktop environment: (`env | grep XDG_CURRENT_DESKTOP`) 55 56#### If applicable 57- Xserver version: (`sudo X -version`) 58- DXVK version: 59- Wine/Proton version: 60 61 62### Regression 63 64Did it used to work in a previous Mesa version? It can greatly help to know when the issue started. 65 66 67### API captures (if applicable, optional) 68 69Consider recording a [GFXReconstruct](https://github.com/LunarG/gfxreconstruct/blob/dev/USAGE_desktop.md) (preferred), [RenderDoc](https://renderdoc.org/), or [apitrace](https://github.com/apitrace/apitrace/blob/master/docs/USAGE.markdown) capture of the issue with the RADV driver active. This can tremendously help when debugging issues, but you're still encouraged to report issues if you can't provide a capture file. 70 71### Further information (optional) 72 73Does the issue reproduce with the LLVM backend (`RADV_DEBUG=llvm`) or on the AMDGPU-PRO drivers? 74 75Does your environment set any of the variables `ACO_DEBUG`, `RADV_DEBUG`, and `RADV_PERFTEST`? 76