“UbuntuHelp:ReportingBugs”的版本间的差异

2007年12月4日 (二) 11:19的版本

文章出处:

https://help.ubuntu.com/community/ReportingBugs

点击翻译:

English

请不要直接编辑翻译本页，本页将定期与来源同步。

Software contains flaws, called bugs. To keep track of bugs and their fixes, Ubuntu uses Launchpad. If you want to help fixing bugs, please see HelpingWithBugs.

Getting started

To create a Launchpad account, go here.

Reporting bugs

The first things you should look at are the following guides about deciding to file a bug or not. If you need help determining which package to file a bug about please read finding the right package. If you need help with debugging a problem, see UbuntuHelp:DebuggingProcedures. If you unsure what information to include in the bug report, http://www.chiark.greenend.org.uk/~sgtatham/bugs.html has quite a lot of information.

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 support requests in launchpad, the Ubuntu forums, the #ubuntu channel on the Freenode IRC server, or the ubuntu-users mailing list.
• Feature and policy discussions should be discussed on the ubuntu-devel mailing list.
• Development ideas should be discussed on the 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 existing bugs and the release notes for your version of Ubuntu. Release notes can be found at Ubuntu 6.06 LTS, Ubuntu 6.10, Ubuntu 7.04 or Ubuntu 7.10. If it has not been reported and you are running Feisty or a later release, the best way to file the bug is via the application's Help -> Report a Problem menu item. This will start an automated bug filing process that will gather some information about your system and the application in which you are reporting the bug. Alternatively, you can report a new bug directly and manually specify the package. If you do not know the package, read finding the right package or ask someone on #ubuntu-bugs on the Freenode IRC server. Then fill out the description with as much information as you can, including the version of Ubuntu you are using and steps for someone else to recreate the bug. It is better to have too much information in the description than not enough. Once you have filled out the package name, summary and description, click on "Submit Bug Report". When entering your initial description of the bug it is not possible to add attachments. However, after you have clicked "Submit Bug Report" it is then possible to add attachments. Unless you are experienced, it is best if you leave the other fields blank or with their default information. You are now done with your initial report but will mostly likely be contacted for more information about your bug.

• File the bug on one package only and submit only one bug per report. If after reading finding the right package you still aren't positive, file it on "Ubuntu" but it may not receive attention as quickly.
• Do not file it in a release (Dapper/Edgy/Feisty/Gutsy), just on the source package in Ubuntu.
• For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vv", "lspci -vvn" and "dmesg" will help.
• For display/X problems, always attach /etc/X11/xorg.conf and /var/log/Xorg.0.log.

NOTE: Most kubuntu specific packages are listed here

English error messages

If you are getting error messages in a language other than English, it can often be helpful to put the English version of the message in the bug report. You can do this by running the program from a terminal with "LANGUAGE=C" before its name. For example, if "sudo apt-get update" is not working properly,

LANGUAGE=C sudo apt-get update

Bug triage

Bug triage is the act of gathering information to complete a bug report, cleaning up old bugs, and solving some. More information on bug triage can be found at the Bug Squad's team page.