Bug-Buddy | ||
---|---|---|
<<< Previous | Next >>> |
The Short subject for the bug report section will be used at the start of the emailed bug report. You do not need the package name in it as you have already assigned that. But being specific is good. "Crash when I try to save" or "Forgets my preferences" is much better than "Bug". Hackers will read these summaries when looking for something they can fix, and clear one-sentence summaries will catch their attention.
The Full description of the bug section is where you describe what you did, what happened, and what you expected to happen. Good things to include:
Exact copies of any error messages;
Your window manager name and version (especially if the bug involves moving things around the screen or mouse focus problems);
If you can make it happen in one way, and not in another way, include that. If there are two ways to do something (a menu selection and a typed command, for example), and only one triggers the bug, definitely include that;
Why you think it is a bug. What should have happened instead? Whilst this is obvious for some things, ("It shouldn't crash when I try to save the file") it is not obvious for others. "If it can't save the file, it should tell me so that I don't keep editing it without realising I am wasting my effort".
Sometimes screenshots can be helpful. Please do not send one in a bug-buddy report! But if you have one, mention that you have it, so that a bug-fixer who would like to see it can email you about it.
If you have any suggestions on what caused it or how to fix it, wonderful. If not, don't worry. Just explain what happened. If a developer needs more information, s/he can mail you back for it.
<<< Previous | Home | Next >>> |
Report Information | More information |