ReportingBugs

Differences between revisions 1 and 6 (spanning 5 versions)
⇤ ← Revision 1 as of 2005-10-07 04:52:00 →
Size: 1278
Editor: 94
Comment:
← Revision 6 as of 2005-12-27 01:18:24 → ⇥
Size: 2916
Editor: S0106001217cbd164
Comment: add link to debugging, and links to malone/bugzilla
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Your problem may not get fixed unless you file a bug report. Software contains flaws, called bugs. To manage them, Ubuntu currently uses two bug tracking systems:
Line 3: Line 3:
In some sense, it is better to file a useless bug report than to let a bug continue to exist. Before filing, please take a few minutes and search for a similar bug on bugzilla.ubuntu.com. You may also click the Bug Report Tool from the Applications - System tools menu. '''If you want to help fixing bugs, please see HelpingWithBugs'''
Line 5: Line 5:
If you find a bug which resebmles your's, add to it. == Bug trackers ==
=== Bugzilla ===
Bugzilla is a bug tracker developed by the Mozilla Project. It is used by Ubuntu for tracking all of the bugs in packages which are supported (in {{{main}}} and {{{restricted}}})
Line 7: Line 9:
Try to file a thoughtful bug report. You should be informative, but that does not mean that you have to fix the bug before filing your report. It is okay to not know what to do to fix it. The Ubuntu Bugzilla can be found here: http://bugzilla.ubuntu.com/
Line 9: Line 11:
If your bug report is compelling, it will be assigned to someone and you will be prompted to add information to the bug report thread. You will be given clear instructions on how to gather relevant information. === Malone ===
Line 11: Line 13:
It is very satisfying to file a bug report which ends up making a difference. Malone is a new bug tracker created as part of the Launchpad architecture. Malone is currently used to track all bug for non-supported packages ({{{universe}}} and {{{multiverse}}})
Line 13: Line 15:
Malone can be found here: https://launchpad.net/distros/ubuntu/+bugs
Line 14: Line 17:
== Getting started ==
Line 15: Line 19:
Be sure to '''not''' file bug reports for the following:
{{{
Support requests: You should use the forums, IRC or the Ubuntu-users mailing lists.		 In order to start using either Bugzilla or Malone, you need an account.
Line 19: Line 21:
=== Bugzilla ===
Line 20: Line 23:
Feature and policy discussions: This should be brought up on the Ubuntu-devel mailing list, IRC or create a wiki page. To create an account in Bugzilla, go [https://bugzilla.ubuntu.com/createaccount.cgi here]
Line 22: Line 25:
=== Malone ===
Line 23: Line 27:
Development ideas: Make such suggestions directly to the developers on the ubuntu-devel mailing list.
}}}		 Malone uses the Launchpad login, which is the same as this wiki. To create a Launchpad account, go [https://launchpad.net/distros/ubuntu/+bugs/+login here]

== Filing Bugs ==

Once you have an account on one (or both) of the bug trackers, time to ask the critical questions. The first thing you should do is look at the following guides about when to file a bug or not.

If you need help with debugging a problem, see ["Debugging"]

=== When to file a bug ===

 * You can repeat the problem
 * It is not a feature of the program

=== When to not file a bug ===

 * Support requests should go to the [http://www.ubuntuforums.org/ forums], #ubuntu on irc, or the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-users ubuntu-users] mailing list.
 * Feature and policy discussions should be discussed on the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel ubuntu-devel] mailing list.
 * Development ideas should be discussed on the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel ubuntu-devel] mailing list.

=== Actually filing the bug ===

So your bug is an actual bug. The first thing you should do is search for it being already reported. If it is not, then click on the '''New''' link for Bugzilla or the '''Report a bug''' for Malone. Try and fill out a useful summary, select which program it happened in. If you do not know, take a guess or ask someone. Then fill out the description with as much information as you can. It is better to have more information that too little. Once you have filed out the package name, summary and description, click on submit. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done.

== Bug triage ==

Bug triage is the act of cleaning up old bugs, solving some, and closing those which are incorrectly filed. Information on bug triage can be found at HelpingWithBugs.

CategoryDocumentation

Software contains flaws, called bugs. To manage them, Ubuntu currently uses two bug tracking systems:

If you want to help fixing bugs, please see HelpingWithBugs

Bug trackers

Bugzilla

Bugzilla is a bug tracker developed by the Mozilla Project. It is used by Ubuntu for tracking all of the bugs in packages which are supported (in main and restricted)

The Ubuntu Bugzilla can be found here: http://bugzilla.ubuntu.com/

Malone

Malone is a new bug tracker created as part of the Launchpad architecture. Malone is currently used to track all bug for non-supported packages (universe and multiverse)

Malone can be found here: https://launchpad.net/distros/ubuntu/+bugs

Getting started

In order to start using either Bugzilla or Malone, you need an account.

Bugzilla

To create an account in Bugzilla, go [https://bugzilla.ubuntu.com/createaccount.cgi here]

Malone

Malone uses the Launchpad login, which is the same as this wiki. To create a Launchpad account, go [https://launchpad.net/distros/ubuntu/+bugs/+login here]

Filing Bugs

Once you have an account on one (or both) of the bug trackers, time to ask the critical questions. The first thing you should do is look at the following guides about when to file a bug or not.

If you need help with debugging a problem, see ["Debugging"]

When to file a bug

  • You can repeat the problem
  • It is not a feature of the program

When to not file a bug

Actually filing the bug

So your bug is an actual bug. The first thing you should do is search for it being already reported. If it is not, then click on the New link for Bugzilla or the Report a bug for Malone. Try and fill out a useful summary, select which program it happened in. If you do not know, take a guess or ask someone. Then fill out the description with as much information as you can. It is better to have more information that too little. Once you have filed out the package name, summary and description, click on submit. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done.

Bug triage

Bug triage is the act of cleaning up old bugs, solving some, and closing those which are incorrectly filed. Information on bug triage can be found at HelpingWithBugs.

CategoryDocumentation

ReportingBugs (last edited 2008-08-06 16:33:09 by localhost)