Merge lp:~bkerensa/serverguide/serverguide-review-A.1 into lp:~ubuntu-core-doc/serverguide/oneiric

Proposed by Benjamin Kerensa
Status: Rejected
Rejected by: Doug Smythies
Proposed branch: lp:~bkerensa/serverguide/serverguide-review-A.1
Merge into: lp:~ubuntu-core-doc/serverguide/oneiric
Diff against target: 334 lines (+9/-318)
1 file modified
serverguide/C/reporting-bugs.xml (+9/-318)
To merge this branch: bzr merge lp:~bkerensa/serverguide/serverguide-review-A.1
Reviewer Review Type Date Requested Status
Peter Matulis Needs Fixing
Review via email: mp+86992@code.launchpad.net

Description of the change

Tidying of:
A.1 -- Reporting Bugs in Ubuntu Server Edition

To post a comment you must log in.
Revision history for this message
Peter Matulis (petermatulis) wrote :

Benjamin, I agree that what we currently have is much too wordy but I would say you are "throwing out the baby with the bathwater" here. The reader should be given information about commands for typical command-line scenarios:

1. Filing a bug
2
. Adding bug info to an existing bug
3
. Saving bug info to disk and transfer to another computer for the actual filing
4. Other?

and then be provided with solid links to follow for more information.

We should focus solely on the command line for interaction with Launchpad. That objective may help guide us for this appendix. There may be tasks done easily on a graphical desktop that is not so obvious in a CLI environment. What challenges does the Server Edition present us with?...

review: Needs Fixing
Revision history for this message
Doug Smythies (dsmythies) wrote :

Can this one be set to "REJECTED" and then deleted?
It is obsolete is it not?

Unmerged revisions

34. By Benjamin Kerensa

Reviewing sub-chapter 6.1; Minor revision in wording to be consistent with wiki

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 2011-05-03 07:11:18 +0000
3+++ serverguide/C/reporting-bugs.xml 2011-12-28 08:34:17 +0000
4@@ -1,321 +1,12 @@
5 <?xml version="1.0" encoding="UTF-8"?>
6-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
7- "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
8-<!ENTITY % globalent SYSTEM "../../libs/global.ent">
9-%globalent;
10-<!ENTITY % gnome-menus-C SYSTEM "../../libs/gnome-menus-C.ent">
11-%gnome-menus-C;
12-<!ENTITY % xinclude SYSTEM "../../libs/xinclude.mod">
13-%xinclude;
14-<!ENTITY language "&EnglishAmerican;">
15-]>
16-<appendix id="serverguide-appendix" status="review">
17- <title>Appendix</title>
18-
19- <sect1 id="reporting-bugs" status="review">
20+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
21+<article lang="">
22+ <sect1>
23+ <title>appendix</title>
24+ <title>Appendix</title>
25+ </sect1>
26+ <sect1>
27 <title>Reporting Bugs in Ubuntu Server Edition</title>
28-
29- <para>
30- While the Ubuntu Project attempts to release software with as few
31- bugs as possible, they do occur. You can help fix these bugs by
32- reporting ones that you find to the project. The Ubuntu Project
33- uses <ulink url="https://launchpad.net/">Launchpad</ulink>
34- to track its bug reports. In order to file a bug
35- about Ubuntu Server on Launchpad, you will need to
36- <ulink url="https://help.launchpad.net/YourAccount/NewAccount">create
37- an account</ulink>.
38- </para>
39-
40- <sect2 id="reporting-bugs-ubuntu-bug" status="review">
41- <title>Reporting Bugs With ubuntu-bug</title>
42-
43- <para>
44- The preferred way to report a bug is with the
45- <application>ubuntu-bug</application> command. The ubuntu-bug
46- tool gathers information about the system useful to developers in
47- diagnosing the reported problem that will then be included in the
48- bug report filed on Launchpad. Bug reports in Ubuntu need to be
49- filed against a specific software package, thus the name of the
50- package that the bug occurs in needs to be given to ubuntu-bug:
51- </para>
52-
53-<screen>
54-<command>ubuntu-bug PACKAGENAME</command>
55-</screen>
56-
57- <para>
58- For example, to file a bug against the openssh-server package, you would do:
59- </para>
60-
61-<screen>
62-<command>ubuntu-bug openssh-server</command>
63-</screen>
64-
65- <para>
66- You can specify either a binary package or the source package
67- for ubuntu-bug. Again using openssh-server as an example,
68- you could also generate the report against the source package
69- for openssh-server, openssh:
70- </para>
71-
72-<screen>
73-<command>ubuntu-bug openssh</command>
74-</screen>
75-
76- <note>
77- <para>
78- See <xref linkend="package-management"/>
79- for more information about packages in Ubuntu.
80- </para>
81- </note>
82-
83- <para>
84- The ubuntu-bug command will gather information about the system in
85- question, possibly including information specific to the specified
86- package, and then ask you what you would like to do with collected
87- information:
88- </para>
89-
90-<screen>
91-<command>ubuntu-bug postgresql</command>
92-
93-*** Collecting problem information
94-
95-The collected information can be sent to the developers to improve the
96-application. This might take a few minutes.
97-..........
98-
99-*** Send problem report to the developers?
100-
101-After the problem report has been sent, please fill out the form in the
102-automatically opened web browser.
103-
104-What would you like to do? Your options are:
105- S: Send report (1.7 KiB)
106- V: View report
107- K: Keep report file for sending later or copying to somewhere else
108- C: Cancel
109-Please choose (S/V/K/C):
110-</screen>
111-
112- <para>
113- The options available are:
114- </para>
115-
116- <para>
117- <itemizedlist>
118- <listitem>
119- <para><emphasis role="bold">Send Report</emphasis> Selecting
120- Send Report submits the collected information to Launchpad as
121- part of the the process of filing a bug report. You will be
122- given the opportunity to describe the situation that led up to
123- the occurrence of the bug.
124- </para>
125-
126-<screen>
127-*** Uploading problem information
128-
129-The collected information is being sent to the bug tracking system.
130-This might take a few minutes.
131-91%
132-
133-*** To continue, you must visit the following URL:
134-
135- https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+filebug/kc6eSnTLnLxF8u0t3e56EukFeqJ?
136-
137-You can launch a browser now, or copy this URL into a browser on another
138-computer.
139-
140-Choices:
141- 1: Launch a browser now
142- C: Cancel
143-Please choose (1/C):
144-</screen>
145-
146- <para>
147- If you choose to start a browser, by default the text based web
148- browser <application>w3m</application> will be used to finish filing
149- the bug report. Alternately, you can copy the given URL to a
150- currently running web browser.
151- </para>
152- </listitem>
153-
154- <listitem>
155- <para>
156- <emphasis role="bold">View Report</emphasis> Selecting View
157- Report causes the collected information to be displayed to
158- the terminal for review.
159- </para>
160-
161-<screen>
162-Package: postgresql 8.4.2-2
163-PackageArchitecture: all
164-Tags: lucid
165-ProblemType: Bug
166-ProcEnviron:
167- LANG=en_US.UTF-8
168- SHELL=/bin/bash
169-Uname: Linux 2.6.32-16-server x86_64
170-Dependencies:
171- adduser 3.112ubuntu1
172- base-files 5.0.0ubuntu10
173- base-passwd 3.5.22
174- coreutils 7.4-2ubuntu2
175-...
176-</screen>
177-
178- <para>
179- After viewing the report, you will be brought back to the same
180- menu asking what you would like to do with the report.
181- </para>
182- </listitem>
183-
184- <listitem>
185- <para>
186- <emphasis role="bold">Keep Report File</emphasis> Selecting Keep
187- Report File causes the gathered information to be written to
188- a file. This file can then be used to later file a bug report
189- or transferred to a different Ubuntu system for reporting.
190- To submit the report file, simply give it as an argument to
191- the ubuntu-bug command:
192- </para>
193-
194-<screen>
195-What would you like to do? Your options are:
196- S: Send report (1.7 KiB)
197- V: View report
198- K: Keep report file for sending later or copying to somewhere else
199- C: Cancel
200-Please choose (S/V/K/C): <userinput>k</userinput>
201-Problem report file: /tmp/apport.postgresql.v4MQas.apport
202-
203-<command>ubuntu-bug /tmp/apport.postgresql.v4MQas.apport</command>
204-
205-*** Send problem report to the developers?
206-...
207-</screen>
208- </listitem>
209-
210- <listitem>
211- <para>
212- <emphasis role="bold">Cancel</emphasis> Selecting
213- Cancel causes the collected information to be discarded.
214- </para>
215- </listitem>
216- </itemizedlist>
217- </para>
218- </sect2>
219-
220- <sect2 id="apport-crash-catching" status="review">
221- <title>Reporting Application Crashes</title>
222-
223- <para>
224- The software package that provides the ubuntu-bug utility,
225- <application>apport</application>, can be configured to trigger
226- when applications crash. This is disabled by default, as capturing
227- a crash can be resource intensive depending on how much memory
228- the application that crashed was using as apport captures and
229- processes the core dump.
230- </para>
231-
232- <para>
233- Configuring apport to capture information about
234- crashing applications requires a couple of steps. First,
235- <application>gdb</application> needs to be installed; it is not
236- installed by default in Ubuntu Server Edition.
237- </para>
238-
239-<screen>
240-<command>sudo apt-get install gdb</command>
241-</screen>
242-
243- <para>
244- See <xref linkend="package-management"/>
245- for more information about managing packages in Ubuntu.
246- </para>
247-
248- <para>
249- Once you have ensured that gdb is installed, open the file
250- <filename>/etc/default/apport</filename> in your text editor,
251- and change the <emphasis>enabled</emphasis> setting to be
252- <emphasis role="bold">1</emphasis> like so:
253- </para>
254-
255-<programlisting>
256-# set this to 0 to disable apport, or to 1 to enable it
257-# you can temporarily override this with
258-# sudo service apport start force_start=1
259-enabled=<userinput>1</userinput>
260-
261-# set maximum core dump file size (default: 209715200 bytes == 200 MB)
262-maxsize=209715200
263-</programlisting>
264-
265- <para>
266- Once you have completed editing
267- <filename>/etc/default/apport</filename>,
268- start the apport service:
269- </para>
270-
271-<screen>
272-<command>sudo start apport</command>
273-</screen>
274-
275- <para>
276- After an application crashes, use the
277- <application>apport-cli</application> command to search for the
278- existing saved crash report information:
279- </para>
280-
281-<screen>
282-<command>apport-cli</command>
283-
284-*** dash closed unexpectedly on 2010-03-11 at 21:40:59.
285-
286-If you were not doing anything confidential (entering passwords or other
287-private information), you can help to improve the application by
288-reporting
289-the problem.
290-
291-What would you like to do? Your options are:
292- R: Report Problem...
293- I: Cancel and ignore future crashes of this program version
294- C: Cancel
295-Please choose (R/I/C):
296-</screen>
297-
298- <para>
299- Selecting <emphasis>Report Problem</emphasis> will walk you through
300- similar steps as when using ubuntu-bug. One important difference
301- is that a crash report will be marked as private when filed on
302- Launchpad, meaning that it will be visible to only a limited set
303- of bug triagers. These triagers will review the gathered data for private
304- information before making the bug report publicly visible.
305- </para>
306-
307- <!-- Include a bit here on using apport-retrace for generating a
308- full stack trace locally, for situations when the application
309- does contain confidential information that should not be
310- submitted to launchpad? -->
311-
312- </sect2>
313-
314- <sect2 id="reporting-bugs-resources" status="review">
315- <title>Resources</title>
316- <itemizedlist>
317- <listitem>
318- <para>
319- See the <ulink url="https://help.ubuntu.com/community/ReportingBugs">Reporting
320- Bugs</ulink> Ubuntu wiki page.
321- </para>
322- </listitem>
323- <listitem>
324- <para>
325- Also, the <ulink url="https://wiki.ubuntu.com/Apport">Apport</ulink> page has some useful information. Though some
326- of it pertains to using a GUI.
327- </para>
328- </listitem>
329- </itemizedlist>
330- </sect2>
331+ <para>While the Ubuntu Project attempts to release software with as few bugs as possible, they do occur. You can help fix these bugs by reporting ones that you find to the project. The Ubuntu Project uses <ulink url="https://launchpad.net/">Launchpad</ulink> to track its bug reports. In order to file a bug about Ubuntu Server on Launchpad, you will need to <ulink url="https://help.launchpad.net/YourAccount/NewAccount">create an account</ulink>. </para>
332 </sect1>
333-</appendix>
334+</article>

Subscribers

People subscribed via source and target branches