17ec681f3SmrgReport a Bug 27ec681f3Smrg============ 37ec681f3Smrg 47ec681f3SmrgTo file a Mesa bug, go to `GitLab on 57ec681f3Smrgfreedesktop.org <https://gitlab.freedesktop.org/mesa/mesa/-/issues>`__. 67ec681f3Smrg 77ec681f3SmrgPlease follow these bug reporting guidelines: 87ec681f3Smrg 97ec681f3Smrg- Check if a new version of Mesa is available which might have fixed 107ec681f3Smrg the problem. 117ec681f3Smrg- Check if your bug is already reported in the database. 127ec681f3Smrg- Monitor your bug report for requests for additional information, etc. 137ec681f3Smrg- Attach the output of running glxinfo or wglinfo. This will tell us 147ec681f3Smrg the Mesa version, which device driver you're using, etc. 157ec681f3Smrg- If you're reporting a crash, try to use your debugger (gdb) to get a 167ec681f3Smrg stack trace. Also, recompile Mesa in debug mode to get more detailed 177ec681f3Smrg information. 187ec681f3Smrg- Describe in detail how to reproduce the bug, especially with games 197ec681f3Smrg and applications that the Mesa developers might not be familiar with. 207ec681f3Smrg- Provide an `apitrace <https://github.com/apitrace/apitrace>`__ or 217ec681f3Smrg simple GLUT-based test program if possible. 227ec681f3Smrg 237ec681f3SmrgThe easier a bug is to reproduce, the sooner it will be fixed. Please do 247ec681f3Smrgeverything you can to facilitate quickly fixing bugs. If your bug report 257ec681f3Smrgis vague or your test program doesn't compile easily, the problem may 267ec681f3Smrgnot be fixed very quickly. 27