Merge lp:~petermatulis/serverguide/review_reporting-bugs into lp:serverguide/trunk
- review_reporting-bugs
- Merge into trunk
Proposed by
Peter Matulis
Status: | Merged |
---|---|
Approved by: | Doug Smythies |
Approved revision: | 207 |
Merged at revision: | 210 |
Proposed branch: | lp:~petermatulis/serverguide/review_reporting-bugs |
Merge into: | lp:serverguide/trunk |
Diff against target: |
463 lines (+158/-206) 1 file modified
serverguide/C/reporting-bugs.xml (+158/-206) |
To merge this branch: | bzr merge lp:~petermatulis/serverguide/review_reporting-bugs |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Doug Smythies | Approve | ||
Review via email: mp+227398@code.launchpad.net |
Commit message
Description of the change
Same as the one pushed to Utopic.
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1 | === modified file 'serverguide/C/reporting-bugs.xml' | |||
2 | --- serverguide/C/reporting-bugs.xml 2013-03-23 22:09:27 +0000 | |||
3 | +++ serverguide/C/reporting-bugs.xml 2014-07-18 20:40:54 +0000 | |||
4 | @@ -14,74 +14,57 @@ | |||
5 | 14 | <title>Reporting Bugs in Ubuntu Server Edition</title> | 14 | <title>Reporting Bugs in Ubuntu Server Edition</title> |
6 | 15 | 15 | ||
7 | 16 | <para> | 16 | <para> |
16 | 17 | While the Ubuntu Project attempts to release software with as few | 17 | The Ubuntu Project, and thus Ubuntu Server, uses <ulink url="https://launchpad.net/">Launchpad</ulink> |
17 | 18 | bugs as possible, they do occur. You can help fix these bugs by | 18 | as its bugtracker. In order to file a bug, you will need a Launchpad account. <ulink url="https://help.launchpad.net/YourAccount/NewAccount">Create |
18 | 19 | reporting ones that you find to the project. The Ubuntu Project | 19 | one here</ulink> if necessary. |
11 | 20 | uses <ulink url="https://launchpad.net/">Launchpad</ulink> | ||
12 | 21 | to track its bug reports. In order to file a bug | ||
13 | 22 | about Ubuntu Server on Launchpad, you will need to | ||
14 | 23 | <ulink url="https://help.launchpad.net/YourAccount/NewAccount">create | ||
15 | 24 | an account</ulink>. | ||
19 | 25 | </para> | 20 | </para> |
20 | 26 | 21 | ||
55 | 27 | <sect2 id="reporting-bugs-ubuntu-bug" status="review"> | 22 | <sect2 id="reporting-bugs-apport-cli" status="review"> |
56 | 28 | <title>Reporting Bugs With ubuntu-bug</title> | 23 | <title>Reporting Bugs With apport-cli</title> |
57 | 29 | 24 | ||
58 | 30 | <para> | 25 | <para> |
59 | 31 | The preferred way to report a bug is with the | 26 | The preferred way to report a bug is with the <application>apport-cli</application> command. It must be invoked on the machine affected by the bug |
60 | 32 | <application>ubuntu-bug</application> command. The ubuntu-bug | 27 | because it collects information from the system on which it is being run and publishes it to the bug report on Launchpad. Getting that information to |
61 | 33 | tool gathers information about the system useful to developers in | 28 | Launchpad can therefore be a challenge if the system is not running a desktop environment in order to use a browser (common with servers) or if it does |
62 | 34 | diagnosing the reported problem that will then be included in the | 29 | not have Internet access. The steps to take in these situations are described below. |
63 | 35 | bug report filed on Launchpad. Bug reports in Ubuntu need to be | 30 | </para> |
64 | 36 | filed against a specific software package, thus the name of the | 31 | |
65 | 37 | package that the bug occurs in needs to be given to ubuntu-bug: | 32 | <note> |
66 | 38 | </para> | 33 | <para> |
67 | 39 | 34 | The commands <application>apport-cli</application> and <application>ubuntu-bug</application> should give the same results on a CLI server. | |
68 | 40 | <screen> | 35 | The latter is actually a symlink to <application>apport-bug</application> which is intelligent enough to know whether a desktop environment is in use and |
69 | 41 | <command>ubuntu-bug PACKAGENAME</command> | 36 | will choose <application>apport-cli</application> if not. Since server systems tend to be CLI-only apport-cli was chosen from the outset in this guide. |
70 | 42 | </screen> | 37 | </para> |
71 | 43 | 38 | </note> | |
72 | 44 | <para> | 39 | |
73 | 45 | For example, to file a bug against the openssh-server package, you would do: | 40 | <para> |
74 | 46 | </para> | 41 | Bug reports in Ubuntu need to be filed against a specific software package, so the name of the |
75 | 47 | 42 | package (source package or program name/path) affected by the bug needs to be supplied to apport-cli: | |
76 | 48 | <screen> | 43 | </para> |
77 | 49 | <command>ubuntu-bug openssh-server</command> | 44 | |
78 | 50 | </screen> | 45 | <screen> |
79 | 51 | 46 | <command>apport-cli PACKAGENAME</command> | |
46 | 52 | <para> | ||
47 | 53 | You can specify either a binary package or the source package | ||
48 | 54 | for ubuntu-bug. Again using openssh-server as an example, | ||
49 | 55 | you could also generate the report against the source package | ||
50 | 56 | for openssh-server, openssh: | ||
51 | 57 | </para> | ||
52 | 58 | |||
53 | 59 | <screen> | ||
54 | 60 | <command>ubuntu-bug openssh</command> | ||
80 | 61 | </screen> | 47 | </screen> |
81 | 62 | 48 | ||
82 | 63 | <note> | 49 | <note> |
83 | 64 | <para> | 50 | <para> |
86 | 65 | See <xref linkend="package-management"/> | 51 | See <xref linkend="package-management"/> for more information about packages in Ubuntu. |
85 | 66 | for more information about packages in Ubuntu. | ||
87 | 67 | </para> | 52 | </para> |
88 | 68 | </note> | 53 | </note> |
89 | 69 | 54 | ||
90 | 70 | <para> | 55 | <para> |
95 | 71 | The ubuntu-bug command will gather information about the system in | 56 | Once apport-cli has finished gathering information you will be asked what to do with it. For |
96 | 72 | question, possibly including information specific to the specified | 57 | instance, to report a bug in vim: |
93 | 73 | package, and then ask you what you would like to do with collected | ||
94 | 74 | information: | ||
97 | 75 | </para> | 58 | </para> |
98 | 76 | 59 | ||
99 | 77 | <screen> | 60 | <screen> |
101 | 78 | <command>ubuntu-bug postgresql</command> | 61 | <command>apport-cli vim</command> |
102 | 79 | 62 | ||
103 | 80 | *** Collecting problem information | 63 | *** Collecting problem information |
104 | 81 | 64 | ||
105 | 82 | The collected information can be sent to the developers to improve the | 65 | The collected information can be sent to the developers to improve the |
106 | 83 | application. This might take a few minutes. | 66 | application. This might take a few minutes. |
108 | 84 | .......... | 67 | ... |
109 | 85 | 68 | ||
110 | 86 | *** Send problem report to the developers? | 69 | *** Send problem report to the developers? |
111 | 87 | 70 | ||
112 | @@ -89,117 +72,115 @@ | |||
113 | 89 | automatically opened web browser. | 72 | automatically opened web browser. |
114 | 90 | 73 | ||
115 | 91 | What would you like to do? Your options are: | 74 | What would you like to do? Your options are: |
117 | 92 | S: Send report (1.7 KiB) | 75 | S: Send report (2.8 KB) |
118 | 93 | V: View report | 76 | V: View report |
119 | 94 | K: Keep report file for sending later or copying to somewhere else | 77 | K: Keep report file for sending later or copying to somewhere else |
120 | 78 | I: Cancel and ignore future crashes of this program version | ||
121 | 95 | C: Cancel | 79 | C: Cancel |
123 | 96 | Please choose (S/V/K/C): | 80 | Please choose (S/V/K/I/C): |
124 | 97 | </screen> | 81 | </screen> |
125 | 98 | 82 | ||
126 | 99 | <para> | 83 | <para> |
128 | 100 | The options available are: | 84 | The first three options are described below: |
129 | 101 | </para> | 85 | </para> |
130 | 102 | 86 | ||
131 | 103 | <para> | 87 | <para> |
132 | 104 | <itemizedlist> | 88 | <itemizedlist> |
133 | 105 | <listitem> | 89 | <listitem> |
139 | 106 | <para><emphasis role="bold">Send Report</emphasis> Selecting | 90 | <para><emphasis role="bold">Send:</emphasis> |
140 | 107 | Send Report submits the collected information to Launchpad as | 91 | submits the collected information to Launchpad as part of the process |
141 | 108 | part of the process of filing a bug report. You will be | 92 | of filing a new bug report. You will be given the opportunity to describe |
142 | 109 | given the opportunity to describe the situation that led up to | 93 | the bug in your own words. |
138 | 110 | the occurrence of the bug. | ||
143 | 111 | </para> | 94 | </para> |
144 | 112 | 95 | ||
145 | 113 | <screen> | 96 | <screen> |
146 | 97 | |||
147 | 114 | *** Uploading problem information | 98 | *** Uploading problem information |
148 | 115 | 99 | ||
149 | 116 | The collected information is being sent to the bug tracking system. | 100 | The collected information is being sent to the bug tracking system. |
150 | 117 | This might take a few minutes. | 101 | This might take a few minutes. |
152 | 118 | 91% | 102 | 94% |
153 | 119 | 103 | ||
154 | 120 | *** To continue, you must visit the following URL: | 104 | *** To continue, you must visit the following URL: |
155 | 121 | 105 | ||
160 | 122 | https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+filebug/kc6eSnTLnLxF8u0t3e56EukFeqJ? | 106 | https://bugs.launchpad.net/ubuntu/+source/vim/+filebug/09b2495a-e2ab-11e3-879b-68b5996a96c8? |
161 | 123 | 107 | ||
162 | 124 | You can launch a browser now, or copy this URL into a browser on another | 108 | You can launch a browser now, or copy this URL into a browser on another computer. |
163 | 125 | computer. | 109 | |
164 | 126 | 110 | ||
165 | 127 | Choices: | 111 | Choices: |
166 | 128 | 1: Launch a browser now | 112 | 1: Launch a browser now |
167 | 129 | C: Cancel | 113 | C: Cancel |
217 | 130 | Please choose (1/C): | 114 | Please choose (1/C): <userinput>1</userinput> |
218 | 131 | </screen> | 115 | </screen> |
219 | 132 | 116 | ||
220 | 133 | <para> | 117 | <para> |
221 | 134 | If you choose to start a browser, by default the text based web | 118 | The browser that will be used when choosing '1' will be the one known on the system as |
222 | 135 | browser <application>w3m</application> will be used to finish filing | 119 | <application>www-browser</application> via the |
223 | 136 | the bug report. Alternately, you can copy the given URL to a | 120 | <ulink url="http://manpages.ubuntu.com/manpages/en/man8/update-alternatives.8.html"> |
224 | 137 | currently running web browser. | 121 | Debian alternatives system</ulink>. Examples of text-based browsers to install include <application>links</application>, |
225 | 138 | </para> | 122 | <application>elinks</application>, <application>lynx</application>, and <application>w3m</application>. |
226 | 139 | </listitem> | 123 | You can also manually point an existing browser at the given URL. |
227 | 140 | 124 | </para> | |
228 | 141 | <listitem> | 125 | </listitem> |
229 | 142 | <para> | 126 | |
230 | 143 | <emphasis role="bold">View Report</emphasis> Selecting View | 127 | <listitem> |
231 | 144 | Report causes the collected information to be displayed to | 128 | <para> |
232 | 145 | the terminal for review. | 129 | <emphasis role="bold">View:</emphasis> |
233 | 146 | </para> | 130 | displays the collected information on the screen for review. This can |
234 | 147 | 131 | be a lot of information. Press 'Enter' to scroll by screenful. Press 'q' | |
235 | 148 | <screen> | 132 | to quit and return to the choice menu. |
236 | 149 | Package: postgresql 8.4.2-2 | 133 | </para> |
237 | 150 | PackageArchitecture: all | 134 | </listitem> |
238 | 151 | Tags: lucid | 135 | |
239 | 152 | ProblemType: Bug | 136 | <listitem> |
240 | 153 | ProcEnviron: | 137 | <para> |
241 | 154 | LANG=en_US.UTF-8 | 138 | <emphasis role="bold">Keep:</emphasis> |
242 | 155 | SHELL=/bin/bash | 139 | writes the collected information to disk. The resulting file can be later used to |
243 | 156 | Uname: Linux 2.6.32-16-server x86_64 | 140 | file the bug report, typically after transferring it to another Ubuntu system. |
195 | 157 | Dependencies: | ||
196 | 158 | adduser 3.112ubuntu1 | ||
197 | 159 | base-files 5.0.0ubuntu10 | ||
198 | 160 | base-passwd 3.5.22 | ||
199 | 161 | coreutils 7.4-2ubuntu2 | ||
200 | 162 | ... | ||
201 | 163 | </screen> | ||
202 | 164 | |||
203 | 165 | <para> | ||
204 | 166 | After viewing the report, you will be brought back to the same | ||
205 | 167 | menu asking what you would like to do with the report. | ||
206 | 168 | </para> | ||
207 | 169 | </listitem> | ||
208 | 170 | |||
209 | 171 | <listitem> | ||
210 | 172 | <para> | ||
211 | 173 | <emphasis role="bold">Keep Report File</emphasis> Selecting Keep | ||
212 | 174 | Report File causes the gathered information to be written to | ||
213 | 175 | a file. This file can then be used to later file a bug report | ||
214 | 176 | or transferred to a different Ubuntu system for reporting. | ||
215 | 177 | To submit the report file, simply give it as an argument to | ||
216 | 178 | the ubuntu-bug command: | ||
244 | 179 | </para> | 141 | </para> |
245 | 180 | 142 | ||
246 | 181 | <screen> | 143 | <screen> |
247 | 182 | What would you like to do? Your options are: | 144 | What would you like to do? Your options are: |
249 | 183 | S: Send report (1.7 KiB) | 145 | S: Send report (2.8 KB) |
250 | 184 | V: View report | 146 | V: View report |
251 | 185 | K: Keep report file for sending later or copying to somewhere else | 147 | K: Keep report file for sending later or copying to somewhere else |
252 | 148 | I: Cancel and ignore future crashes of this program version | ||
253 | 186 | C: Cancel | 149 | C: Cancel |
270 | 187 | Please choose (S/V/K/C): <userinput>k</userinput> | 150 | Please choose (S/V/K/I/C): <userinput>k</userinput> |
271 | 188 | Problem report file: /tmp/apport.postgresql.v4MQas.apport | 151 | Problem report file: /tmp/apport.vim.1pg92p02.apport |
272 | 189 | 152 | </screen> | |
273 | 190 | <command>ubuntu-bug /tmp/apport.postgresql.v4MQas.apport</command> | 153 | |
274 | 191 | 154 | <para> | |
275 | 192 | *** Send problem report to the developers? | 155 | To report the bug, get the file onto an internet-enabled Ubuntu system and apply apport-cli |
276 | 193 | ... | 156 | to it. This will cause the menu to appear immediately (the information is already collected). |
277 | 194 | </screen> | 157 | You should then press 's' to send: |
278 | 195 | </listitem> | 158 | </para> |
279 | 196 | 159 | ||
280 | 197 | <listitem> | 160 | <screen> |
281 | 198 | <para> | 161 | <command>apport-cli apport.vim.1pg92p02.apport</command> |
282 | 199 | <emphasis role="bold">Cancel</emphasis> Selecting | 162 | </screen> |
283 | 200 | Cancel causes the collected information to be discarded. | 163 | |
284 | 201 | </para> | 164 | <para> |
285 | 202 | </listitem> | 165 | To directly save a report to disk (without menus) you can do: |
286 | 166 | |||
287 | 167 | <screen> | ||
288 | 168 | <command>apport-cli vim --save apport.vim.test.apport</command> | ||
289 | 169 | </screen> | ||
290 | 170 | |||
291 | 171 | Report names should end in <emphasis>.apport</emphasis> . | ||
292 | 172 | </para> | ||
293 | 173 | |||
294 | 174 | <note> | ||
295 | 175 | <para> | ||
296 | 176 | If this internet-enabled system is non-Ubuntu/Debian, apport-cli is not available so the | ||
297 | 177 | bug will need to be created manually. An apport report is also not to be included as an | ||
298 | 178 | attachment to a bug either so it is completely useless in this scenario. | ||
299 | 179 | </para> | ||
300 | 180 | </note> | ||
301 | 181 | |||
302 | 182 | </listitem> | ||
303 | 183 | |||
304 | 203 | </itemizedlist> | 184 | </itemizedlist> |
305 | 204 | </para> | 185 | </para> |
306 | 205 | </sect2> | 186 | </sect2> |
307 | @@ -207,89 +188,58 @@ | |||
308 | 207 | <sect2 id="apport-crash-catching" status="review"> | 188 | <sect2 id="apport-crash-catching" status="review"> |
309 | 208 | <title>Reporting Application Crashes</title> | 189 | <title>Reporting Application Crashes</title> |
310 | 209 | 190 | ||
368 | 210 | <para> | 191 | <para> |
369 | 211 | The software package that provides the ubuntu-bug utility, | 192 | The software package that provides the apport-cli utility, <application>apport</application>, |
370 | 212 | <application>apport</application>, can be configured to trigger | 193 | can be configured to automatically capture the state of a crashed application. This |
371 | 213 | when applications crash. This is disabled by default, as capturing | 194 | is enabled by default (in <filename>/etc/default/apport</filename>). |
372 | 214 | a crash can be resource intensive depending on how much memory | 195 | </para> |
373 | 215 | the application that crashed was using as apport captures and | 196 | |
374 | 216 | processes the core dump. | 197 | <para> |
375 | 217 | </para> | 198 | After an application crashes, if enabled, apport will store a crash report under <filename>/var/crash</filename>: |
376 | 218 | 199 | </para> | |
377 | 219 | <para> | 200 | |
378 | 220 | Configuring apport to capture information about | 201 | <screen> |
379 | 221 | crashing applications requires a couple of steps. First, | 202 | -rw-r----- 1 peter whoopsie 150K Jul 24 16:17 _usr_lib_x86_64-linux-gnu_libmenu-cache2_libexec_menu-cached.1000.crash |
380 | 222 | <application>gdb</application> needs to be installed; it is not | 203 | </screen> |
381 | 223 | installed by default in Ubuntu Server Edition. | 204 | |
382 | 224 | </para> | 205 | <para> |
383 | 225 | 206 | Use the <application>apport-cli</application> command without arguments to process any pending crash reports. It | |
384 | 226 | <screen> | 207 | will offer to report them one by one. |
385 | 227 | <command>sudo apt-get install gdb</command> | 208 | </para> |
329 | 228 | </screen> | ||
330 | 229 | |||
331 | 230 | <para> | ||
332 | 231 | See <xref linkend="package-management"/> | ||
333 | 232 | for more information about managing packages in Ubuntu. | ||
334 | 233 | </para> | ||
335 | 234 | |||
336 | 235 | <para> | ||
337 | 236 | Once you have ensured that gdb is installed, open the file | ||
338 | 237 | <filename>/etc/default/apport</filename> in your text editor, | ||
339 | 238 | and change the <emphasis>enabled</emphasis> setting to be | ||
340 | 239 | <emphasis role="bold">1</emphasis> like so: | ||
341 | 240 | </para> | ||
342 | 241 | |||
343 | 242 | <programlisting> | ||
344 | 243 | # set this to 0 to disable apport, or to 1 to enable it | ||
345 | 244 | # you can temporarily override this with | ||
346 | 245 | # sudo service apport start force_start=1 | ||
347 | 246 | enabled=<userinput>1</userinput> | ||
348 | 247 | |||
349 | 248 | # set maximum core dump file size (default: 209715200 bytes == 200 MB) | ||
350 | 249 | maxsize=209715200 | ||
351 | 250 | </programlisting> | ||
352 | 251 | |||
353 | 252 | <para> | ||
354 | 253 | Once you have completed editing | ||
355 | 254 | <filename>/etc/default/apport</filename>, | ||
356 | 255 | start the apport service: | ||
357 | 256 | </para> | ||
358 | 257 | |||
359 | 258 | <screen> | ||
360 | 259 | <command>sudo start apport</command> | ||
361 | 260 | </screen> | ||
362 | 261 | |||
363 | 262 | <para> | ||
364 | 263 | After an application crashes, use the | ||
365 | 264 | <application>apport-cli</application> command to search for the | ||
366 | 265 | existing saved crash report information: | ||
367 | 266 | </para> | ||
386 | 267 | 209 | ||
387 | 268 | <screen> | 210 | <screen> |
388 | 269 | <command>apport-cli</command> | 211 | <command>apport-cli</command> |
389 | 270 | 212 | ||
391 | 271 | *** dash closed unexpectedly on 2010-03-11 at 21:40:59. | 213 | *** Send problem report to the developers? |
392 | 272 | 214 | ||
397 | 273 | If you were not doing anything confidential (entering passwords or other | 215 | After the problem report has been sent, please fill out the form in the |
398 | 274 | private information), you can help to improve the application by | 216 | automatically opened web browser. |
395 | 275 | reporting | ||
396 | 276 | the problem. | ||
399 | 277 | 217 | ||
400 | 278 | What would you like to do? Your options are: | 218 | What would you like to do? Your options are: |
402 | 279 | R: Report Problem... | 219 | S: Send report (153.0 KB) |
403 | 220 | V: View report | ||
404 | 221 | K: Keep report file for sending later or copying to somewhere else | ||
405 | 280 | I: Cancel and ignore future crashes of this program version | 222 | I: Cancel and ignore future crashes of this program version |
406 | 281 | C: Cancel | 223 | C: Cancel |
418 | 282 | Please choose (R/I/C): | 224 | Please choose (S/V/K/I/C): <userinput>s</userinput> |
419 | 283 | </screen> | 225 | </screen> |
420 | 284 | 226 | ||
421 | 285 | <para> | 227 | <para> |
422 | 286 | Selecting <emphasis>Report Problem</emphasis> will walk you through | 228 | If you send the report, as was done above, the prompt will be returned immediately and the |
423 | 287 | similar steps as when using ubuntu-bug. One important difference | 229 | <filename>/var/crash</filename> directory will then contain 2 extra files: |
424 | 288 | is that a crash report will be marked as private when filed on | 230 | </para> |
425 | 289 | Launchpad, meaning that it will be visible to only a limited set | 231 | |
426 | 290 | of bug triagers. These triagers will review the gathered data for private | 232 | <screen> |
427 | 291 | information before making the bug report publicly visible. | 233 | -rw-r----- 1 peter whoopsie 150K Jul 24 16:17 _usr_lib_x86_64-linux-gnu_libmenu-cache2_libexec_menu-cached.1000.crash |
428 | 292 | </para> | 234 | -rw-rw-r-- 1 peter whoopsie 0 Jul 24 16:37 _usr_lib_x86_64-linux-gnu_libmenu-cache2_libexec_menu-cached.1000.upload |
429 | 235 | -rw------- 1 whoopsie whoopsie 0 Jul 24 16:37 _usr_lib_x86_64-linux-gnu_libmenu-cache2_libexec_menu-cached.1000.uploaded | ||
430 | 236 | </screen> | ||
431 | 237 | |||
432 | 238 | <para> | ||
433 | 239 | Sending in a crash report like this will not immediately result in the creation of a new public bug. | ||
434 | 240 | The report will be made private on Launchpad, meaning that it will be visible to only a limited set | ||
435 | 241 | of bug triagers. These triagers will then scan the report for possible private data before creating a public bug. | ||
436 | 242 | </para> | ||
437 | 293 | 243 | ||
438 | 294 | <!-- Include a bit here on using apport-retrace for generating a | 244 | <!-- Include a bit here on using apport-retrace for generating a |
439 | 295 | full stack trace locally, for situations when the application | 245 | full stack trace locally, for situations when the application |
440 | @@ -301,18 +251,20 @@ | |||
441 | 301 | <sect2 id="reporting-bugs-resources" status="review"> | 251 | <sect2 id="reporting-bugs-resources" status="review"> |
442 | 302 | <title>Resources</title> | 252 | <title>Resources</title> |
443 | 303 | <itemizedlist> | 253 | <itemizedlist> |
444 | 254 | |||
445 | 304 | <listitem> | 255 | <listitem> |
446 | 305 | <para> | 256 | <para> |
449 | 306 | See the <ulink url="https://help.ubuntu.com/community/ReportingBugs">Reporting | 257 | See the <ulink url="https://help.ubuntu.com/community/ReportingBugs">Reporting Bugs</ulink> Ubuntu wiki page. |
448 | 307 | Bugs</ulink> Ubuntu wiki page. | ||
450 | 308 | </para> | 258 | </para> |
451 | 309 | </listitem> | 259 | </listitem> |
452 | 260 | |||
453 | 310 | <listitem> | 261 | <listitem> |
454 | 311 | <para> | 262 | <para> |
456 | 312 | Also, the <ulink url="https://wiki.ubuntu.com/Apport">Apport</ulink> page has some useful information. Though some | 263 | Also, the <ulink url="https://wiki.ubuntu.com/Apport">Apport</ulink> page has some useful information. Though some |
457 | 313 | of it pertains to using a GUI. | 264 | of it pertains to using a GUI. |
458 | 314 | </para> | 265 | </para> |
459 | 315 | </listitem> | 266 | </listitem> |
460 | 267 | |||
461 | 316 | </itemizedlist> | 268 | </itemizedlist> |
462 | 317 | </sect2> | 269 | </sect2> |
463 | 318 | </sect1> | 270 | </sect1> |
Peter, it looks good thanks. I couldn't submit a test bug report against the "Ubuntu Server Guide" because it is not a package. I did submit one against "docbook" and it is pending, and I hope it will delete by itself after some time when I don't finish it.