[deployment-guide] Applied Mirek's changes to the ABRT chapter.
Jaromir Hradilek
jhradile at fedoraproject.org
Sun Oct 2 13:48:10 UTC 2011
commit bd3cccb6e738fb46aa970bfd3c59164240a60c8a
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Sun Oct 2 15:29:30 2011 +0200
Applied Mirek's changes to the ABRT chapter.
en-US/Automatic_Bug_Reporting_Tool_ABRT.xml | 69 +++++++++++++++++---
en-US/images/abrt-gui_rhtsupport_configuration.png | Bin 0 -> 12085 bytes
en-US/images/abrt-gui_rhtsupport_reporting.png | Bin 0 -> 61563 bytes
en-US/images/abrt-gui_rhtsupport_warning.png | Bin 0 -> 17543 bytes
en-US/images/abrt-gui_select_reporter.png | Bin 55173 -> 60629 bytes
5 files changed, 60 insertions(+), 9 deletions(-)
---
diff --git a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
index 6e3bd4a..1093dc8 100644
--- a/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
+++ b/en-US/Automatic_Bug_Reporting_Tool_ABRT.xml
@@ -14,9 +14,6 @@
<para>
For Red Hat Enterprise Linux 6.2, the Automatic Bug Reporting Tool has been upgraded to version 2.0. The <application>ABRT</application> 2-series brings major improvements to automatic bug detection and reporting.
</para>
- <para>For more information on the major differences between the <application>ABRT</application> 1-series and <application>ABRT</application> 2-series,<!--as well as easy migration instructions,--> refer to the <citetitle>Red Hat Enterprise Linux 6.2 Release Notes</citetitle>.</para>
- <!--<para>For more information on the major differences between the <application>ABRT</application> 1-series and <application>ABRT</application> 2-series, as well as easy migration instructions, refer to <xref linkend="sect-migration_to_abrt2"/>
- </para>-->
</important>
<para>
<application>ABRT</application> is the <application>Automatic Bug Reporting Tool</application>. <application>ABRT</application> consists of a daemon, <systemitem
@@ -74,7 +71,7 @@
</section>
<section
id="sect-abrt-installation">
- <title>Installing <application>ABRT</application> and Starting the abrtd Service</title>
+ <title>Installing <application>ABRT</application> and Starting its Services</title>
<para>
As the first step in order to use <application>ABRT</application>, you should ensure that the <package>abrt-desktop</package> package is installed on your system by running the following command as the root user:
</para>
@@ -88,7 +85,7 @@
linkend="sec-Installing"/>
</para>
<para>
- Your next step should be to verify that the <systemitem
+ Your next step should be to verify that <systemitem
class="daemon">abrtd</systemitem> is running. The daemon is typically configured to start up at boot time. You can use the following command as root to verify its current status:
</para>
<screen>~]# <command>service abrtd status</command>
@@ -302,7 +299,7 @@ kernel.panic = 0</screen>
</mediaobject>
</figure>
<para>
- You are first asked to provide additional information about the problem which occurred. You should provide detailed information on how the problem happened and what steps should be done in order to reproduce it. In the next steps, choose how the problem will be analyzed and generate a backtrace depending on your configuration. You can skip the analysis and backtrace-generation steps.
+ You are first asked to provide additional information about the problem which occurred. You should provide detailed information on how the problem happened and what steps should be done in order to reproduce it. In the next steps, choose how the problem will be analyzed and generate a backtrace depending on your configuration. You can skip the analysis and backtrace-generation steps but remember that developers need as much information about the problem as possible. You can always modify the backtrace and remove any sensitive information you do not want to provide before you send the problem data out.
</para>
<figure
id="fig-abrt-gui_select_analyzer">
@@ -334,7 +331,7 @@ kernel.panic = 0</screen>
</textobject>
</mediaobject>
</figure>
- <para>Next, choose how you want to report the issue.</para>
+ <para>Next, choose how you want to report the issue. If you are using Red Hat Enterprise Linux, Red Hat Customer Support is the preferred choice. </para>
<figure
id="fig-abrt-gui_select_reporter">
<title>Selecting a problem reporter.</title>
@@ -350,7 +347,43 @@ kernel.panic = 0</screen>
</textobject>
</mediaobject>
</figure>
- <para>Finally, review the backtrace and confirm the data to be reported.</para>
+ <para>
+ If you choose to report to Red Hat Customer Support, and you have not configured this event yet, you will be warned that this event is not configured properly and you will be offered an option to do so.
+ </para>
+ <figure
+ id="fig-abrt-gui_rhtsupport_warning">
+ <title>Warning - missing Red Hat Customer Support configuration.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/abrt-gui_rhtsupport_warning.png"
+ format="PNG"
+ scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>Warning - missing Red Hat Customer Support configuration.</para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <para>
+ Here, you need to provide your Red Hat login information (Refer to <xref linkend="sect-abrt-configuration-event_configuration_in_gui"/> for more information on how to acquire it and how to set this event.), otherwise you will fail to report the problem.
+ </para>
+ <figure
+ id="fig-abrt-gui_rhtsupport_configuration.png">
+ <title>Red Hat Customer Support configuration window.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/abrt-gui_rhtsupport_configuration.png"
+ format="PNG"
+ scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>Red Hat Customer Support configuration window.</para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <para>After you have chosen a reporting method and have it set up correctly, review the backtrace and confirm the data to be reported.</para>
<figure
id="fig-abrt-gui_backtrace_review">
<title>Reviewing the problem backtrace.</title>
@@ -381,6 +414,24 @@ kernel.panic = 0</screen>
</textobject>
</mediaobject>
</figure>
+ <para>
+ Finally, the problem data is sent to the chosen destination, and you can now decide whether to continue with reporting the problem using another available method or finish your work on this problem. If you have reported your problem to the Red Hat Customer Support database, a problem case is filed in the database. From now on, you will be informed about the problem resolution progress via email you provided during the process of reporting. You can also oversee the problem case using the URL that is provided to you by <application>ABRT</application> GUI when the problem case is created, or via emails received from Red Hat Support.
+ </para>
+ <figure
+ id="fig-abrt-gui_rhtsupport_reporting">
+ <title>Problem is being reported to the Red Hat Customer Support database.</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata
+ fileref="images/abrt-gui_rhtsupport_reporting.png"
+ format="PNG"
+ scalefit="0" />
+ </imageobject>
+ <textobject>
+ <para>Problem is being reported to the Red Hat Customer Support database.</para>
+ </textobject>
+ </mediaobject>
+ </figure>
</section>
<section
id="sect-abrt-cli">
@@ -1590,4 +1641,4 @@ ftp> <command>quit</command></screen>
TBD
</para>
</section>-->
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/en-US/images/abrt-gui_rhtsupport_configuration.png b/en-US/images/abrt-gui_rhtsupport_configuration.png
new file mode 100644
index 0000000..6f29d63
Binary files /dev/null and b/en-US/images/abrt-gui_rhtsupport_configuration.png differ
diff --git a/en-US/images/abrt-gui_rhtsupport_reporting.png b/en-US/images/abrt-gui_rhtsupport_reporting.png
new file mode 100644
index 0000000..f88998c
Binary files /dev/null and b/en-US/images/abrt-gui_rhtsupport_reporting.png differ
diff --git a/en-US/images/abrt-gui_rhtsupport_warning.png b/en-US/images/abrt-gui_rhtsupport_warning.png
new file mode 100644
index 0000000..df82826
Binary files /dev/null and b/en-US/images/abrt-gui_rhtsupport_warning.png differ
diff --git a/en-US/images/abrt-gui_select_reporter.png b/en-US/images/abrt-gui_select_reporter.png
index 598ace2..250cba3 100644
Binary files a/en-US/images/abrt-gui_select_reporter.png and b/en-US/images/abrt-gui_select_reporter.png differ
More information about the docs-commits
mailing list