This file is indexed.

/usr/share/doc/kde/HTML/en/kubuntu/bugs/filing-crash.html is in kubuntu-docs 12.04.0ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  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
<html><head><title>Filing a Crash Report</title><link rel="stylesheet" type="text/css" href="help:/common/kde-default.css"><link rel="stylesheet" type="text/css" href="help:/common/kde-docs.css"><link rel="stylesheet" type="text/css" href="help:/common/kde-localised.css"><link rel="stylesheet" type="text/css" href="help:/common/kubuntu.css"><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="Bug Reports"><link rel="up" href="index.html" title="Bug Reports"><link rel="prev" href="bug-trackers.html" title="Bug Trackers Used By Kubuntu"><link rel="next" href="filing-non-crash.html" title="Filing a Non-Crash or Regression Report"><link rel="copyright" href="legal.html" title="Credits and License"><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><meta name="GENERATOR" content="KDE XSL Stylesheet V1.14 using libxslt"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div id="content"><div id="header"><div id="header_content"><div id="header_left"><div id="header_right"><img src="help:/common/top-kde.jpg" width="36" height="34"> Filing a Crash Report</div></div></div></div><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="bug-trackers.html">Prev</a></td><td class="upCell"> </td><td class="nextCell"><a accesskey="n" href="filing-non-crash.html">Next</a></td></tr></table></div><div id="contentBody"><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="filing-crash"></a>Filing a Crash Report</h2></div></div></div><p>
When an application crashes in <span>Kubuntu</span>, the appropriate crash dialog will
appear. It is usually easy to file a bug report from the dialog. With a 
<span class="trademark">KDE</span>&#8482; application, the <span class="trademark">KDE</span>&#8482; crash 
dialog will appear along with instructions for reporting the bug. Otherwise, 
the <span>Ubuntu</span> crash dialog will appear with instructions for filing a bug on 
<span class="trademark">Launchpad</span>&#8482;.
</p><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="filing-crash-kde"></a>KDE</h3></div></div></div><p>
When an application crashes in <span class="trademark">KDE</span>&#8482;, a crash dialog will 
be presented that is similar to the following images. The first image shows the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guilabel">General</span></span> tab, which provides an overview of the crash. The
second image shows the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guilabel">Developer Information</span></span> tab, which
provides trace information that is useful to developers.
</p><p>
</p><div class="example"><a name="idp4631288"></a><p class="title"><b>Example 1. KDE Crash Dialog (General tab)</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_dialog_general_tab.png"><hr></div></div></div><p><br class="example-break">
</p><p>
</p><div class="example"><a name="idp4632656"></a><p class="title"><b>Example 2. KDE Crash Dialog (Developer Information tab)</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_dialog_devinfo_tab.png"><hr></div></div></div><p><br class="example-break">
</p><p>
If the trace information is deemed valuable, filing a bug report is easy with 
the crash dialog wizard. If the trace is not deemed valuable, then it is not 
possible to file a bug report with the wizard. The bug report can still be 
filed manually at <a class="ulink" href="https://bugs.kde.org/" target="_top">https://bugs.kde.org/</a>.
</p><p>
To complete the bug reporting process, follow the procedure below.
</p><div class="procedure"><a name="idp4634888"></a><p class="title"><b>Procedure 1. Filing the bug report after a crash</b></p><ol class="procedure" type="1"><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Report Bug</span></span> button.
The following dialog will appear:
</p><p>
</p><div class="example"><a name="idp4636520"></a><p class="title"><b>Example 3. Welcome to the Reporting Assistant</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_welcome.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Next</span></span> button. The
following dialog will appear:
</p><p>
</p><div class="example"><a name="idp4639256"></a><p class="title"><b>Example 4. What do you know about the crash?</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_about_crash.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
Select the applicable options. The drop-down box under the question,
<span class="quote">&#8220;<span class="quote"><span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guilabel">Does the application crash again if you repeat the
same situation?</span></span></span>&#8221;</span> has several options.
</p><p>
</p><div class="example"><a name="idp4641752"></a><p class="title"><b>Example 5. Does the application crash again if you repeat the same situation?</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_about_crash_dropdown.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
After selecting the applicable items from the dialog in the previous step,
<span class="mousebutton">click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Next</span></span> button.
</p></li><li class="step"><p>
Depending on the information available in the crash report, either of two 
dialogs will appear. One is a dialog that indicates that there is not enough
information to file a good report. The other is a dialog indicating that the
information is useful and that it would be helpful to continue with filing the
report.
</p><p>
</p><div class="example"><a name="idp4645400"></a><p class="title"><b>Example 6. Not enough information for developers to continue the reporting 
process</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_not_enough_info.png"><hr></div></div></div><p><br class="example-break">
</p><p>
</p><div class="example"><a name="idp4646872"></a><p class="title"><b>Example 7. This crash information is useful</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_useful_information.png"><hr></div></div></div><p><br class="example-break">
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">If there was not enough information...</h3><p>
It may be necessary to install the proper debug packages in order to get a good
trace. Such packages include <code class="filename">kdebase-dbg</code>,
<code class="filename">kdebase-workspace-dbg</code>, and 
<code class="filename">kdebase-runtime-dbg</code>.
</p></div></li><li class="step"><p>
If enough information was provided to continue filing a bug report using
the assistant, a dialog will appear to allow logging in to 
<span class="trademark">KDE</span>&#8482;'s <span class="trademark">Bugzilla</span>&#8482;.
</p><p>
</p><div class="example"><a name="idp6282720"></a><p class="title"><b>Example 8. KDE Bug Tracking System Login</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_bugtracker_login.png"><hr></div></div></div><p><br class="example-break">
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Use e-mail address as username</h3><p>
Use the email address that was used to register with 
<span class="trademark">KDE</span>&#8482;'s <span class="trademark">Bugzilla</span>&#8482;.
</p></div></li><li class="step"><p>
After logging in with your username (email address) and password, 
<span class="mousebutton">click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Login</span></span> button. The
assistant will check for duplicates and display the following dialog:
</p><p>
</p><div class="example"><a name="idp6286832"></a><p class="title"><b>Example 9. Bug Report Possible Duplicates List</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_possible_duplicates.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
If there is a possible duplicate report, <span class="mousebutton">click</span> the
report in the list and then <span class="mousebutton">click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Open
selected report</span></span> button. Either of the following dialogs will be
presented:
</p><p>
</p><div class="example"><a name="idp6289984"></a><p class="title"><b>Example 10. The report you selected is already marked as a duplicate of 
bug...</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_nested_duplicate_detected.png"><hr></div></div></div><p><br class="example-break">
</p><p>
</p><div class="example"><a name="idp6291456"></a><p class="title"><b>Example 11. Showing the duplicate bug report you selected</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_duplicate_report.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
If the bug appears to be a duplicate, <span class="mousebutton">click</span> the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Add as a possible duplicate</span></span> button. This will file the
bug report and inform the developers that it may be a duplicate. This is
recommended, except in cases with experienced users where it is clearly not a
duplicate. <span class="mousebutton">Clicking</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Attach to this
report (Advanced)</span></span> button will attach the crash information to the 
report.
</p><p>
If the bug is not a duplicate, simply <span class="mousebutton">click</span>
the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Next</span></span> button in the dialog showing the possible 
duplicates. A dialog will appear with <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Let me check more 
reports</span></span>. To prevent checking for more reports and continue filing 
the report, <span class="mousebutton">click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">There
are no real duplicates</span></span> button. A dialog will appear asking you to 
enter additional information concerning the report.
</p><p>
</p><div class="example"><a name="idp8021944"></a><p class="title"><b>Example 12. Details of the Bug Report</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_report_details.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
Once the details of the bug report are complete, 
<span class="mousebutton">click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Next</span></span> button. The 
following dialog will be presented:
</p><p>
</p><div class="example"><a name="idp8024576"></a><p class="title"><b>Example 13. Preview Report</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_report_details_preview.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
If the information looks correct, <span class="mousebutton">click</span> the
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Next</span></span> button. The following dialog will be presented:
</p><p>
</p><div class="example"><a name="idp8027200"></a><p class="title"><b>Example 14. Send Crash Report</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/crash_report_assistant_report_filed.png"><hr></div></div></div><p><br class="example-break">
</p></li></ol></div><p>
<span class="emphasis"><em>Congratulations on a successful bug report!</em></span> Identifying 
and reporting bugs are essential to improving <span>Kubuntu</span> and 
<span class="trademark">KDE</span>&#8482;. Some emails may be sent to the registered address 
to update progress or to allow developers to get additional information about 
the bug.
</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="filing-crash-lp"></a>Launchpad</h3></div></div></div><p>
When an application that is not <span class="trademark">KDE</span>&#8482; crashes in 
<span>Kubuntu</span>, a pop-up notification will appear from 
<span class="application">Apport</span> that is similar to the following image:
</p><p>
</p><div class="example"><a name="idp8031528"></a><p class="title"><b>Example 15. Apport Crash Pop-pup Notification</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-notification.png"><hr></div></div></div><p><br class="example-break">
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Crash information may be different</h3><p>
The screen shots below were created by crashing the application 
<span class="application">VLC</span> deliberately. Crash dialogs associated with 
other applications will be different. In an actual bug situation, the 
application name, <span class="application">VLC</span>, will be replaced by the name 
of the application that actually crashed.
</p></div><p>
To complete the bug reporting process, follow the procedure below.
</p><div class="procedure"><a name="idp8034496"></a><p class="title"><b>Procedure 2. Filing the bug report after a crash</b></p><ol class="procedure" type="1"><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Details</span></span> buttons on
the <span class="application">System Notification Helper</span>. The following dialog
will be presented:
</p><p>
</p><div class="example"><a name="idp8036344"></a><p class="title"><b>Example 16. Sorry, the program "vlc" closed unexpectedly.</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-dialog-1.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Report Problem...</span></span>
button. The <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guilabel">Collecting Problem Information</span></span> progress dialog
will be presented.
</p><p>
</p><div class="example"><a name="idp8039296"></a><p class="title"><b>Example 17. Collecting Problem Information</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-dialog-collecting-info.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
After all information concerning the crash is collected, a dialog will be 
presented that displays the details of the report, and the report is sent to
the developers. <span class="mousebutton">Click</span> the 
<span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Details...</span></span> button to view details of the report. The
following dialog will be presented:
</p><p>
</p><div class="example"><a name="idp8042048"></a><p class="title"><b>Example 18. Send problem report to the developers? (Details)</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-dialog-details.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Send</span></span> button to send
the report to the developers. In this case, it will send the report to 
<span class="trademark">Launchpad</span>&#8482;. The following progress dialog will be presented:
</p><p>
</p><div class="example"><a name="idp8045008"></a><p class="title"><b>Example 19. Uploading problem information</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-dialog-uploading.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
After the progress dialog completes, the default web browser will open to
<span class="trademark">Launchpad</span>&#8482;, presenting either the log-in page or the 
beginning of the online version of the bug reporting process. After logging in 
(if necessary), the following page will be presented:
</p><p>
</p><div class="example"><a name="idp8047440"></a><p class="title"><b>Example 20. Please wait while bug data is processed...</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-browser-processing.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
When <span class="trademark">Launchpad</span>&#8482; is finished processing the bug data, the 
following page will be presented:
</p><p>
</p><div class="example"><a name="idp8049712"></a><p class="title"><b>Example 21. Extra debug information will be added...</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-browser-step-1.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Next</span></span> button. The
following page will be presented:
</p><p>
</p><div class="example"><a name="idp8052256"></a><p class="title"><b>Example 22. Further information</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-browser-step-2.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
Any extra information about the bug report can be filled in to describe, for 
example, what was being done when the application crashed or the online file 
locations that may have caused the crash. The following is a brief description 
filed with the report in this procedure:
</p><p>
</p><div class="example"><a name="idp8054360"></a><p class="title"><b>Example 23. Further information (Completed)</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-browser-step-3.png"><hr></div></div></div><p><br class="example-break">
</p></li><li class="step"><p>
<span class="mousebutton">Click</span> the <span xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="guiitem"><span class="guibutton">Submit Bug Report</span></span>
button on the bottom of the page. The following page will be presented:
</p><p>
</p><div class="example"><a name="idp8056920"></a><p class="title"><b>Example 24. Thank you for your bug report</b></p><div class="example-contents"><div xmlns:doc="http://nwalsh.com/xsl/documentation/1.0" class="mediaobject"><hr><img src="help:/images/C/apport-browser-step-4.png"><hr></div></div></div><p><br class="example-break">
</p></li></ol></div><p>
<span class="emphasis"><em>Congratulations on making a successful crash report!</em></span> 
Identifying and reporting bugs are essential to improving <span>Kubuntu</span>. Some 
emails may be sent to the registered address to update progress or to allow 
developers to get additional information about the bug.
</p></div></div></div><div id="footer"><div class="navCenter"><table class="navigation"><tr><td class="prevCell"><a accesskey="p" href="bug-trackers.html">Prev</a></td><td class="upCell"><a accesskey="h" href="index.html">Home</a></td><td class="nextCell"><a accesskey="n" href="filing-non-crash.html">Next</a></td></tr><tr><td class="prevCell">Bug Trackers Used By <span>Kubuntu</span> </td><td class="upCell"> </td><td class="nextCell"> Filing a Non-Crash or Regression Report</td></tr></table></div><div id="footer_text"><br><a href="mailto:ubuntu-docs@lists.ubuntu.com" class="footer_email">
	  Ubuntu Documentation Project
        </a></div></div></div></body></html>