1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>4. Reporting Bugs and Requesting Enhancements</title>
<link rel="stylesheet" href="gimp-help-plain.css" type="text/css" />
<link rel="stylesheet" href="gimp-help-screen.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.66.1" />
<link rel="start" href="index.html" title=" " />
<link rel="up" href="ch01.html" title="Chapter 1. Introduction" />
<link rel="prev" href="ch01s03.html" title="3. Gimp History" />
<link rel="next" href="ch01s04s02.html" title="4.2. Reporting the Bug" />
</head>
<body>
<div xmlns="" class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center" id="chaptername">4. Reporting Bugs and Requesting Enhancements</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td>
<th width="60%" align="center" id="sectionname">4. Reporting Bugs and Requesting Enhancements</th>
<td width="20%" align="right"> <a accesskey="n" href="ch01s04s02.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="gimp-introduction-bugs"></a>4. Reporting Bugs and Requesting Enhancements</h2>
</div>
</div>
</div>
<a id="id3304389" class="indexterm"></a>
<p>
Sad to say, no version of Gimp has yet been absolutely perfect.
Even sadder, it is likely that no version ever will be. In spite
of all efforts to make everything work, a program as complicated
as Gimp is bound to screw things up occasionally, or even crash.
</p>
<p>
But the fact that bugs are unavoidable does not mean that they
should be passively accepted. If you find a bug in Gimp, the
developers would like to know about it so they can at least try to
fix it.
</p>
<p>
Suppose, then, that you have found a bug, or at least think you
have: you try to do something, and the results are not what you
expect. What should you do? How should you report it?
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25">
<img alt="[Note]" src="../images/note.png" />
</td>
<th align="left">Note</th>
</tr>
<tr>
<td colspan="2" align="left" valign="top">
<p>
The procedure for making an <span class="emphasis"><em>enhancement
request</em></span>–that is, for asking the developers to add a
missing feature–is nearly the same as the procedure for
reporting a bug. The only thing you do differently is to mark the
report as an "enhancement" at the appropriate stage, as described
below.
</p>
</td>
</tr>
</table>
</div>
<p>
In common with many other free software projects, Gimp uses a
bug-reporting mechanism called <span class="emphasis"><em>Bugzilla</em></span>.
This is a very powerful web-based system, capable of managing thousands of
bug reports without losing track. In fact, Gimp shares its
Bugzilla database with the entire Gnome project. At the time this
is being written, Gnome Bugzilla contains 148632 bug reports–no,
make that 148633.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="id3303427"></a>4.1. Making sure it's a Bug</h3>
</div>
</div>
</div>
<p>
The first thing you should do, before reporting a bug, is to make
an effort to verify that what you are seeing really
<span class="emphasis"><em>is</em></span> a bug. It is hard to give a method for
doing this that applies to all situations, but reading the
documentation will often be useful, and discussing the question on
IRC or a mailing list may also be quite helpful. If you are
seeing a <span class="emphasis"><em>crash</em></span>, as opposed to mere
misbehavior, the odds that it is a true bug are pretty high: well
written software programs are not designed to crash under
<span class="emphasis"><em>any</em></span> circumstances. In any case, if you have
made an conscientious effort to decide whether it is really a bug,
and at the end still aren't sure, then please go ahead and report
it: the worst that can happen is that you will waste a bit of
time for the development team.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25">
<img alt="[Note]" src="../images/note.png" />
</td>
<th align="left">Note</th>
</tr>
<tr>
<td colspan="2" align="left" valign="top">
<p>
Actually there are a few things that are known to cause Gimp to
crash but have turned out to be too inconvenient to be worth
fixing. One of them is asking Gimp to do something that requires
vast amounts of memory, such as creating an image one million
pixels on a side.
</p>
</td>
</tr>
</table>
</div>
<p>
You should also make sure that you are using an up-to-date version
of Gimp: reporting bugs that have already been fixed is just a
waste of everybody's time. (Gimp 1 is no longer maintained, so if
you use it and find bugs, either upgrade to Gimp 2 or live with
them.) Particularly if you are using the development version of
Gimp, make sure that you can see the bug in the latest release
before filing a report.
</p>
<p>
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 bugzilla query page (http://bugzilla.gnome.org/query.cgi),
and try to see whether somebody else has already reported the same
thing. The query page allows you to search the bug database in a
variety of ways. Unfortunately this page is a bit more
complicated to use than it really ought to be, but here is
basically what you should do:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term">Summary:</span>
</dt>
<dd>
<p>
Set this to "contains any of the words/strings".
</p>
</dd>
<dt>
<span class="term">(the adjoining entry area)</span>
</dt>
<dd>
<p>
Give one or more words that somebody would be likely to use in
writing a one-sentence summary of a bug similar to yours. For
example, if the problem is that zooming too much causes Gimp
to crash, the word "zoom" would be good.
</p>
</dd>
<dt>
<span class="term">Product:</span>
</dt>
<dd>
<p>
Set this to "GIMP"
</p>
</dd>
<dt>
<span class="term">Component:, Version:, Target:</span>
</dt>
<dd>
<p>
Don't do anything for these.
</p>
</dd>
<dt>
<span class="term">Text information:</span>
</dt>
<dd>
<p>
For now, leave this alone. If your search does not turn up
anything, it might be worth entering your search terms in the
"comment" area here, but this often turns out to give you
either great masses of stuff or nothing.
</p>
</dd>
<dt>
<span class="term">Status:</span>
</dt>
<dd>
<p>
This field encodes the status of a bug report: whether it is
still open, has been resolved, etc. You want to see all
relevant bug reports, regardless of status, so you should hold
down the mouse and sweep it across all entries. Leaving it
alone will not work.
</p>
</dd>
</dl>
</div>
<p>
When you have set these things up, click on the "Search" button at
either the top or bottom; they both do the same thing. The result
is either a list of bug reports–hopefully not too long–or a
message saying "Zarro boogs found". 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 resolved as "Duplicate", don't
be too upset: it has happened repeatedly to the author of this
documentation, who works with Gimp Bugzilla nearly every day.
</p>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="ch01s03.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="ch01.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="ch01s04s02.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">3. Gimp History </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> 4.2. Reporting the Bug</td>
</tr>
</table>
</div>
</body>
</html>
|
