Every good bug report needs exactly four things.
- specify the environment
- steps to reproduce
- what you expected to see
- what you saw instead.
Principles
- be precise
- be clear – explain it so others can reproduce the bug
- one bug per report
- no bug is too trivial to report – small bugs may hide big bugs
- clearly separate fact from speculation
Before you continue, check on the TODO list[link2] and in the FAQ[link3] to see if your bug is already known. If you cannot decode the information on the TODO list, report your problem so we can clarify the TODO list[link4].
To report a security bug, please set the issue in the bug tracker as "private".
Make sure you are running the latest available release before reporting a bug.
[link2]/doc/Dev/TodoList
[link3]/doc/Doc/English/FAQ
[link4]/doc/Org/Questions/Obstacles
[link5]http://www.catb.org/~esr/faqs/smart-questions.html