|
|
54.
|
|
|
This document provides step-by-step procedures for filing <phrase>Kubuntu</phrase> bug reports.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:15(para)
|
|
|
56.
|
|
|
Generally, there are three types of bug reports: <emphasis>crash</emphasis>, <emphasis>non-crash</emphasis>, and <emphasis>feature request</emphasis>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:24(para)
|
|
|
59.
|
|
|
An application or system crash or failure. Most of the time, a crash dialog will be presented that can be turned into a bug report.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:30(para)
|
|
|
60.
|
|
|
Non-crash
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:42(term)
|
|
|
61.
|
|
|
A bug or regression that doesn't cause the application to crash, but does cause the application to stop functioning properly.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:46(para)
|
|
|
62.
|
|
|
Feature request
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:53(term)
|
|
|
63.
|
|
|
Also known as a wish list item, this type of report is filed to add a function to an application, or to change something in the application that isn't due to a regression or a crash.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:57(para)
|
|
|
64.
|
|
|
Bug Trackers Used By <phrase>Kubuntu</phrase>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:57(title)
|
|
|
66.
|
|
|
KDE uses Bugzilla, a "Defect Tracking System". Bugzilla is one of the most popular tools used in the open source development community.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bugs/C/bugs.xml:61(para)
|
|
|
67.
|
|
|
Register first
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
docs/bugs/C/bugs.xml:81(title) docs/bugs/C/bugs.xml:110(title) docs/bugs/C/bugs.xml:672(title)
|
