| Erik Faye-Lund | 4d06683 | 2020-06-12 20:09:42 +0200 | [diff] [blame] | 1 | Report a Bug |
| 2 | ============ |
| 3 | |
| 4 | The Mesa bug database is hosted on |
| 5 | `freedesktop.org <https://freedesktop.org>`__. The old bug database on |
| 6 | SourceForge is no longer used. |
| 7 | |
| 8 | To file a Mesa bug, go to `GitLab on |
| 9 | freedesktop.org <https://gitlab.freedesktop.org/mesa/mesa/-/issues>`__ |
| 10 | |
| 11 | Please follow these bug reporting guidelines: |
| 12 | |
| 13 | - Check if a new version of Mesa is available which might have fixed |
| 14 | the problem. |
| 15 | - Check if your bug is already reported in the database. |
| 16 | - Monitor your bug report for requests for additional information, etc. |
| 17 | - Attach the output of running glxinfo or wglinfo. This will tell us |
| 18 | the Mesa version, which device driver you're using, etc. |
| 19 | - If you're reporting a crash, try to use your debugger (gdb) to get a |
| 20 | stack trace. Also, recompile Mesa in debug mode to get more detailed |
| 21 | information. |
| 22 | - Describe in detail how to reproduce the bug, especially with games |
| 23 | and applications that the Mesa developers might not be familiar with. |
| 24 | - Provide an `apitrace <https://github.com/apitrace/apitrace>`__ or |
| 25 | simple GLUT-based test program if possible. |
| 26 | |
| 27 | The easier a bug is to reproduce, the sooner it will be fixed. Please do |
| 28 | everything you can to facilitate quickly fixing bugs. If your bug report |
| 29 | is vague or your test program doesn't compile easily, the problem may |
| 30 | not be fixed very quickly. |