@k64 To help you get a better response then to the same issue you created last week, I searched on Google for some bug reporting guidelines.
The title of one of the guidelines says it all: How to write a bug report that will make your engineers love you.
Most guidelines have a few steps in common:
- A short but informative headline that includes a short description of the issue
- Description of environment.
For instance, platform and software versions. - When did you first notice the bug?
For instance, after upgrading to version… - Where does the bug appear?
- List the steps you take to reproduce the bug? Be specific.
- Can the bug be reproduced over and over or only sporadically?
- What are the exact error messages that you are receiving?
- Is there any other relevant error information to report?