How to write a good bug report?

[eltos]

Important: There is no customer support.
This software is provided by volunteers in their spare time. We expect you to value our time and to first investigate the problem yourself, try different cases, and gather all the information that will help us understand the cause of the problem and solve it! If you are unable or unwilling to do so, please refrain from opening a ticket, as this will not yield any results and will waste both your and our time.

• Before opening an issue, make sure it has not already been reported by searching the list of issues, including closed issues. If you find your issue has already been reported, only comment if you have valuable information to add. Commenting "Same problem here" is not helpful.
• When opening a new issue, use the templates provided and fill in the information requested therein.
• Describe the bug, the expected behaviour and what you actually observed as detailed as possible.
• If we cannot reproduce the issue, we will likely not be able to fix it. It is therefore crucial that you track down the issue and provide a minimal way how it can be reproduced. Describe the (minimal) steps to reproduce the bug. Keep in mind, that the issue might be related to the specific setup of your personal computer, therefore also try to reproduce it on a different computer or ask a friend if they observe the same.
• Paste the full stack trace, console output or log showing the error message(s). Check Windows Event Viewer, Reliability Monitor, or create and analyse a crash dump. You can find plenty of information how to use these tools on the web.
• Try to investigate the issue and provide any reasonable ideas for a possible solution. For example, if the issue changes when you do one of the reproduction steps a little different. If you figured out a workaround, let us know about it.

Please note that we might close issues that do not provide sufficient information or cannot be reproduced. Once you updated your issue with the required information, feel free to re-open it.