| 2. Reporting the Bug | ||
|---|---|---|
|
Appendiks B. Reporting Bugs and Requesting Enhancements |  |
| 2. Reporting the Bug | ||
|---|---|---|
|
|
Appendiks B. Reporting Bugs and Requesting Enhancements | |
Okay, so you have done everything you could to make sure, and you still think it's probably a bug. You should then go ahead and file a bug report on the GitLab page.
![[Bemærk]](images/note.png)
|
Bemærk |
|---|---|
|
The first time you file a bug report, you will be asked to create a GitLab account. The process is easy and painless, and you probably won't even get any spam as a result. |
File a New Issue
Go to https://gitlab.gnome.org/GNOME/gimp/issues, and select .
If you are not logged in, you are automatically redirected to the login page. After entering your user name (login) and password, you get back to the “New Issue” page.
Fill out the Template
Select and choose whether you plan to report a bug or to request a feature. Note that most of the information you enter can be changed later by the developers if you get it wrong, so try to get it right but don't be obsessive about it.
Give a one-sentence summary that is descriptive enough so that somebody searching for similar bugs would find your bug report on the basis of the words this summary contains.
Describe the problem. Be as specific as you can, try to provide all the information requested from you, and include all information that you think might possibly be relevant. The classic totally useless bug report is, “GIMP crashes. This program sucks”. There is no hope that the developers can solve a problem if they can't tell what it is.
Sometimes it is very helpful to augment a bug report with a screenshot or some other type of data. If you need to do this, click on the button , and follow the directions. But please don't do this unless you think the attachment is really going to be useful—and if you need to attach a screenshot, don't make it any larger than necessary. Bug reports are likely to remain on the system for years, so there is no sense in wasting memory.
When you have filled out all of these things, press the button and your bug report will be submitted. It will be assigned a number, which you may want to make note of; you will, however, be emailed any time somebody makes a comment on your bug report or otherwise alters it, so you will receive reminders in any case. You can see the current state of your bug report at any time by going to https://gitlab.gnome.org/GNOME/gimp/issues/.
