ReportingBugs

Differences between revisions 1 and 18 (spanning 17 versions)
⇤ ← Revision 1 as of 2005-10-07 04:52:00 →
Size: 1278
Editor: 94
Comment:
← Revision 18 as of 2006-06-06 13:37:41 → ⇥
Size: 3443
Editor: CPE-144-136-118-234
Comment: adding normal link for bugs to go to.
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. ## page was renamed from BugReports
Software contains flaws, called bugs. To manage them, Ubuntu uses the [https://launchpad.net/malone Malone] bug tracking system.
Line 3: Line 4:
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 6:
If you find a bug which resebmles your's, add to it. == Malone ==
Line 7: Line 8:
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. Malone is a new bug tracker created as part of the Launchpad architecture. Malone is used to track all bugs for Ubuntu and bugs for packages from other distributions.
Line 9: Line 10:
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. == Getting started ==
Line 11: Line 12:
It is very satisfying to file a bug report which ends up making a difference. 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 ==

The first things you should look at are the following guides about deciding to file a bug or not.

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

If you need help with actually filing the bug, http://www.chiark.greenend.org.uk/~sgtatham/bugs.html has quite a lot of information on how to do it properly.

=== 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 check if it has already been reported by searching through the [https://launchpad.net/distros/ubuntu/+bugs existing bugs]. If it has not been reported, then you can [https://launchpad.net/distros/ubuntu/+filebug report a new bug]. Try and fill out a useful summary and 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 than too little. Once you have filled 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.

 * File the bug on one package only. If you really don't have a clue, file it on "Ubuntu".
 * Do not file it in a release (Breezy/Dapper), just on the source package in [https://launchpad.net/distros/ubuntu/+bugs Ubuntu].
 * For anything hardware related, give precise details. Attach "lspci -vv" output, for instance.
 * For display/X problems, always attach /etc/X11/xorg.conf and /var/log/Xorg.0.log

NOTE: Most kubuntu specific packages are listed [https://launchpad.net/people/kubuntu-team/+packagebugs here]

==== English Error messages ====
If you are getting error messages a language other than english, it can often be help full to put the english version of the message in the bug report. You can do this be running the program from a terminal with "LANGUAGE=C" before its name, for example
{{{
LANGUAGE=C sudo apt-get update
}}}
Line 14: Line 51:
== Bug triage ==
Line 15: Line 53:
Be sure to '''not''' file bug reports for the following:
{{{
Support requests: You should use the forums, IRC or the Ubuntu-users mailing lists.		 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.
Line 19: Line 55:

Feature and policy discussions: This should be brought up on the Ubuntu-devel mailing list, IRC or create a wiki page.


Development ideas: Make such suggestions directly to the developers on the ubuntu-devel mailing list.
}}}		 CategoryDocumentation CategoryCleanup

Software contains flaws, called bugs. To manage them, Ubuntu uses the [https://launchpad.net/malone Malone] bug tracking system.

If you want to help fixing bugs, please see HelpingWithBugs

Malone

Malone is a new bug tracker created as part of the Launchpad architecture. Malone is used to track all bugs for Ubuntu and bugs for packages from other distributions.

Getting started

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

The first things you should look at are the following guides about deciding to file a bug or not.

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

If you need help with actually filing the bug, http://www.chiark.greenend.org.uk/~sgtatham/bugs.html has quite a lot of information on how to do it properly.

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 check if it has already been reported by searching through the [https://launchpad.net/distros/ubuntu/+bugs existing bugs]. If it has not been reported, then you can [https://launchpad.net/distros/ubuntu/+filebug report a new bug]. Try and fill out a useful summary and 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 than too little. Once you have filled 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.

  • File the bug on one package only. If you really don't have a clue, file it on "Ubuntu".

  • Do not file it in a release (Breezy/Dapper), just on the source package in [https://launchpad.net/distros/ubuntu/+bugs Ubuntu].

  • For anything hardware related, give precise details. Attach "lspci -vv" output, for instance.
  • For display/X problems, always attach /etc/X11/xorg.conf and /var/log/Xorg.0.log

NOTE: Most kubuntu specific packages are listed [https://launchpad.net/people/kubuntu-team/+packagebugs here]

English Error messages

If you are getting error messages a language other than english, it can often be help full to put the english version of the message in the bug report. You can do this be running the program from a terminal with "LANGUAGE=C" before its name, for example 

LANGUAGE=C sudo apt-get update

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 CategoryCleanup

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