User Guide

CHAPTER 1. INTRODUCTION 17
it would be helpful to know which window manager you are using. Another question that
could be asked is whether GNOME or KDE (if either) is being used.
Another useful tidbit of information that is valuable for diagnosis is stating exactly
what it is that has caused the problem. Simply saying, “The foo plug-in doesn’t work.”
is not very helpful. Try to be as explicit as possible, “When I clicked ’foo-button’ in the
’bar-plugin’ GIMP told me that such and such didn’t work.”. If the developers don’t know
exactly which part of the GIMP caused the error, or problem you are referring to, they
can’t really help you.
Now that you have gathered all of the information needed for an accurate bug sub-
mission, let’s move on to actually submitting the report.
1.3.2 Where to submit your bug report
There is only one good way submit your report. The The GNOME Bug Tracker. You will
have to set up a user account and then will be able to submit your report. It is vital that
the information provided is accurate.
Now that you’ve submitted a bug report that’s concise, insightful, and just a little
daring, what now? It would be unreasonable to expect the developers to respond to
every report in person, but know that your report has been noted, and, if it can be
reproduced, it will be fixed. Bugs that are not actual bugs (problems that are not related
to code) should be answered for you if someone else can reproduce it, or has had the
same problem before.