|
|
107.
|
|
|
If the bug is not a duplicate, simply <mousebutton>click</mousebutton> the <guibutton>Next</guibutton> in the dialog showing the possible duplicates. A dialog will appear with <guibutton>Let me check more reports</guibutton>. To prevent checking for more reports and continue to file the report, <mousebutton>click</mousebutton> the <guibutton>There are no real duplicates</guibutton> button. A dialog will appear to enter additional information concerning the report.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:320(para)
|
|
|
113.
|
|
|
<emphasis role="bold">Congratulations on a successful bug report!</emphasis> Identifying and reporting bugs are essential to improving <phrase>Kubuntu</phrase> and KDE. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:374(para)
|
|
|
114.
|
|
|
When an application that is not KDE crashes in <phrase>Kubuntu</phrase>, a pop-up notification will appear from <application>Apport</application> that is similar to the following image.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:383(para)
|
|
|
117.
|
|
|
The following screen shots were created by crashing the application <application>VLC</application> deliberately. Crash dialogs associated with other applications will be different. In an actual bug situation, the application name, <application>VLC</application>, will be replaced by the name of the application that actually crashed.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:398(para)
|
|
|
122.
|
|
|
After all of the 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. <mousebutton>Click</mousebutton> the <guibutton>Details...</guibutton> button to view details of the report. The following dialog will be presented.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:445(para)
|
|
|
126.
|
|
|
After the progress dialog completes, the default web browser will open to Launchpad presenting either the login page or the beginning of the online version of the bug reporting process. After logging in (if necessary) the following page will be presented.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:479(para)
|
|
|
132.
|
|
|
Any extra information can be filled in about the bug report such as what was being done when it 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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:526(para)
|
|
|
134.
|
|
|
<mousebutton>Click</mousebutton> the <guibutton>Submit Bug Report</guibutton> button on the bottom of the page. The following page will be presented.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:543(para)
|
|
|
136.
|
|
|
<emphasis role="bold">Congratulations on making a successful crash report!</emphasis>Identifying and reporting bugs are essential to improving <phrase>Kubuntu</phrase>. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:558(para)
|
|
|
138.
|
|
|
If an application has regressed in its functionality, a bug report should be filed on that application. A regress occurs when a function worked in a previous release but in the latest release, it is not working. In most cases, this type of report will be filed by those who have more experience and may be testing beta quality software. However there are situations where a user needs to report an issue with an application that isn't working right, but isn't crashing. The following procedures will help.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:569(para)
|
