附录 B. 提交错误报告和请求改进

目录

1. 确定它的确是个 BUG
2. 提交 BUG

很遗憾,无论哪个版本的 GIMP 都不是完美的。而且更遗憾的是,之后应该也不会出现完美的版本。我们尽最大努力让所有功能都工作正常,但像 GIMP 这样复杂的程序肯定有时候还是可能把事情弄的很糟,甚至出现程序崩溃。

BUG 不可避免并不是说我们只能认命而被迫接受这个现实。如果你在 GIMP 中发现了 BUG,开发者是很希望得到反馈的,这样他们就能尝试着修复它了。

假设你发现了一个 BUG,或者你觉得你遇到了一个:你想做某件事,但结果不尽人意。你可以怎么办呢?怎样提交 BUG 呢?

[提示] 提示

The procedure for making an enhancement request—that is, for asking the developers to add a missing feature—is the same as the procedure for reporting a bug.

In common with many other free software projects, GIMP uses a bug-reporting mechanism called GitLab. This is a very powerful web-based system, capable of managing thousands of bug reports without losing track. In fact, GIMP shares its GitLab database with the entire Gnome project.

1. 确定它的确是个 BUG

这是提交之前首先需要做的事情,要尝试验证你所观察到的的确一个 BUG 。很难针对所有的情况说明应该怎样做,但看看这里的说明还是很有用,另外在 IRC 或者邮件列表上讨论会很有用。如果你看到了程序崩溃,而不只是一个不太正常的反应,那么很有可能这真的就是一个BUG:设计良好的软件不会专门设计它在任何情况下崩溃。无论具体是什么情况,如果你努力想要确定它是否真的是一个 BUG ,但最终还是无法确定,那就去提交它吧:最坏的结果也只是给开发团队浪费一点点时间而已。

[注意] 注意

实际上我们已知有一些情况会导致 GIMP 崩溃,但修复这些问题需要的代价太大,目前来说还不值得。其中包括让 GIMP 去做一些特别占内存的事情,比如创建一个长、宽都是一百万像素的超大图像。

另外你要确定你用的是当前最新版本的 GIMP :如果你提交的问题已经在新版本中解决掉,那就只是在浪费大家的时间而已。(GIMP 1 已经不再维护了,如果你还在用它,那么要么升级到 GIMP 要么就忍着吧。)而如果你用的是开发版(而不是发布版)的 GIMP ,那你要确定你要在最新的发布版中能够产生同样的 BUG ,再去提交。

If after due consideration you still think you have a legitimate bug report or enhancement request, the next step is to go to GIMP's list of issues (https://gitlab.gnome.org/GNOME/gimp/issues/), and try to see whether somebody else has already reported the same thing.

搜索某个 BUG

Enter some (space separated) search terms, e.g.

filter crash

in the "Search or filter results..." text box and press Enter. By default you only see open reports; you can change this by clicking "All" above the search field.

The result is either a list of bug reports – hopefully not too long – or a message saying Sorry, your filter produced no results. If you don't find a related bug report by doing this, it may be worth trying another search with different terms. If in spite of your best efforts, you file a bug report and it ends up being closed as a duplicate, don't be too upset: it has happened repeatedly to the author of this documentation.