个人工具

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

来自Ubuntu中文

跳转至： 导航, 搜索
小
小
第1行： 第1行：
 
{{From|https://help.ubuntu.com/community/ReportingBugs}}
 
{{From|https://help.ubuntu.com/community/ReportingBugs}}
 
{{Languages|UbuntuHelp:ReportingBugs}}
 
{{Languages|UbuntuHelp:ReportingBugs}}
−
Software contains flaws, called bugs. To keep track of bugs and their fixes, Ubuntu uses [https://bugs.launchpad.net/ubuntu Launchpad].
+
Ubuntu uses Launchpad to keep track of bugs and their fixes. To file a bug you first need to [https://launchpad.net/distros/ubuntu/+bugs/+login create an account].
−
'''If you want to help fixing bugs, please see [[UbuntuHelp:HelpingWithBugs|HelpingWithBugs]]'''.
+
== Reporting bugs ==
−
=== Getting started ===
+
The easiest way to report a bug is with the [[UbuntuWiki:Apport|''Apport'']] application. When an application crashes, apport starts automatically and opens an appropriate bug for you to complete in Launchpad. This procedure will provide our developers with rich debugging information that will make it easier for them to fix the problem.
−
To create a Launchpad account, go [https://launchpad.net/distros/ubuntu/+bugs/+login here].
+
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=apport-1.png
−
=== Reporting bugs ===
+
If you want to report a bug on an application that is running ''and responding'', you can access the same apport functionality from the Help menu via '''Help -> Report a problem'''. This method is preferable than filing a bug directly at the Launchpad website because of the debugging information it attaches, even for user interface bugs.
−
The first things you should look at are the following guides about deciding to file a bug or not.
+
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=report-a-problem.png
−
If you need help determining which package to file a bug about please read [[UbuntuWiki:Bugs/FindRightPackage|finding the right package]].
+
Apport is available for Ubuntu 6.10 (Edgy Eft) and later versions.
−
If you need help with debugging a problem, see [[UbuntuHelp:DebuggingProcedures|DebuggingProcedures]].
+
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=filebug-shot.png
−
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.
+
=== Filing from the command line ===
−
==== 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 [https://answers.launchpad.net/ubuntu support requests in launchpad], the [http://www.ubuntuforums.org/ Ubuntu forums], the #ubuntu channel on the [[UbuntuHelp:InternetRelayChat|Freenode IRC]] server, 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] and the release notes for your version of Ubuntu.  Release notes can be found at [[UbuntuWiki:DapperReleaseNotes|Ubuntu 6.06 LTS]], [[UbuntuWiki:EdgyReleaseNotes#head-7348aa0831ef34256bdd066d1d9a1d112a4afa50|Ubuntu 6.10]], [http://www.ubuntu.com/getubuntu/releasenotes/704 Ubuntu 7.04] or [http://www.ubuntu.com/getubuntu/releasenotes/710 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 [https://launchpad.net/distros/ubuntu/+filebug report a new bug] directly and manually specify the package.  If you do not know the package, read [[UbuntuWiki:Bugs/FindRightPackage|finding the right package]] or ask someone on #ubuntu-bugs on the [[UbuntuHelp:InternetRelayChat|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 [[UbuntuWiki:Bugs/FindRightPackage|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 [https://launchpad.net/distros/ubuntu/+bugs 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 [https://launchpad.net/people/kubuntu-team/+packagebugs 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,
+
 
<pre><nowiki>
 
<pre><nowiki>
−
LANGUAGE=C sudo apt-get update
+
apport-cli -f -p PACKAGE</nowiki></pre>
−
</nowiki></pre>
+
Lets you file a bug against a known package and automatically include all the useful debug information. Use
−
=== Bug triage ===
+
<pre><nowiki>
−
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 [[UbuntuWiki:BugSquad/|page]].
+
apport-cli -f -P PID</nowiki></pre>  
−
[[category:CategoryDocumentation]] [[category:CategoryCleanup]]
+
If you want to file against a running program with a known Process ID (PID) (see '''System -> Administration -> System Monitor''').
 +
=== Filing bugs at Launchpad.net ===
 +
If for some reason you cannot file a bug through the ''Apport'' tool you can file one via [https://launchpad.net/distros/ubuntu/ Launchpad] (Apport is not available on version 6.10 and older). When doing so please ensure that you have determined which package it should be filed against. Read '[[UbuntuWiki:Bugs/FindRightPackage|finding the right package]]' for guidance.
 +
=== Writing a useful report ===
 +
Fill in the description field with as much information as you can, including the release 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. 
 +
Only describe a single problem per bug report so that each can be followed up on in detail. If you experience several issues file separate reports.
 +
Add supporting attachments to explain or help others reproduce your bug. This might include a screen shot or video capture of the problem or a sample document that triggers the fault.
 +
You can only add attachments after the bug has been filed with a title and description. Use the '''Add a comment/attachment''' at the bottom of the page.
 +
For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vvnn" and "dmesg", after a fresh boot, will help a lot.
 +
== When not to file a bug ==
 +
* '''Support requests''' should go to [https://answers.launchpad.net/ubuntu support requests in launchpad], the [http://www.ubuntuforums.org/ Ubuntu forums], the #ubuntu channel on the [[UbuntuHelp:InternetRelayChat|Freenode IRC]] server, or the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-users ubuntu-users] mailing list.
 +
* '''Feature and policy discussions''' (including suggestions to change defaults) should be discussed on the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss ubuntu-devel-discuss] mailing list.
 +
* '''Development ideas''' should be discussed on the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss ubuntu-devel-discuss] mailing list.
 +
* '''Already filed''' - Please check if it has already been reported by searching through the [https://launchpad.net/distros/ubuntu/+bugs existing bugs] and the release notes for your release of Ubuntu [[UbuntuWiki:DapperReleaseNotes|6.06 (Dapper Drake)]], [[UbuntuWiki:EdgyReleaseNotes#head-7348aa0831ef34256bdd066d1d9a1d112a4afa50|6.10 (Edgy Eft)]], [http://www.ubuntu.com/getubuntu/releasenotes/704 7.04 (Feisty Fawn)], [http://www.ubuntu.com/getubuntu/releasenotes/710 7.10 (Gutsy Gibbon)].  
 +
== Getting advice ==
 +
If you need help in finding the right package or providing appropriate information ask someone on #ubuntu-bugs on the [[UbuntuHelp:InternetRelayChat|Freenode IRC]] server or on the [https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad bugsquad mailing list]. 
 +
== Further reading ==
 +
See [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this guide] for general information on writing a good bug report. If you need help with debugging a problem, see [[UbuntuHelp:DebuggingProcedures|DebuggingProcedures]].
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2008年4月23日 (三) 11:55的版本

Geographylogo.png 文章出处: 

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

Geographylogo.png 点击翻译: 

English

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

Ubuntu uses Launchpad to keep track of bugs and their fixes. To file a bug you first need to create an account.

Reporting bugs

The easiest way to report a bug is with the Apport application. When an application crashes, apport starts automatically and opens an appropriate bug for you to complete in Launchpad. This procedure will provide our developers with rich debugging information that will make it easier for them to fix the problem. ReportingBugs?action=AttachFile&do=get&target=apport-1.png If you want to report a bug on an application that is running and responding, you can access the same apport functionality from the Help menu via Help -> Report a problem. This method is preferable than filing a bug directly at the Launchpad website because of the debugging information it attaches, even for user interface bugs. ReportingBugs?action=AttachFile&do=get&target=report-a-problem.png Apport is available for Ubuntu 6.10 (Edgy Eft) and later versions. ReportingBugs?action=AttachFile&do=get&target=filebug-shot.png

Filing from the command line

apport-cli -f -p PACKAGE

Lets you file a bug against a known package and automatically include all the useful debug information. Use 

apport-cli -f -P PID

If you want to file against a running program with a known Process ID (PID) (see System -> Administration -> System Monitor).

Filing bugs at Launchpad.net

If for some reason you cannot file a bug through the Apport tool you can file one via Launchpad (Apport is not available on version 6.10 and older). When doing so please ensure that you have determined which package it should be filed against. Read 'finding the right package' for guidance.

Writing a useful report

Fill in the description field with as much information as you can, including the release 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. Only describe a single problem per bug report so that each can be followed up on in detail. If you experience several issues file separate reports. Add supporting attachments to explain or help others reproduce your bug. This might include a screen shot or video capture of the problem or a sample document that triggers the fault. You can only add attachments after the bug has been filed with a title and description. Use the Add a comment/attachment at the bottom of the page. For anything hardware related, give precise details about your hardware. Attaching the output of "lspci -vvnn" and "dmesg", after a fresh boot, will help a lot.

When not to file a bug

Getting advice

If you need help in finding the right package or providing appropriate information ask someone on #ubuntu-bugs on the Freenode IRC server or on the bugsquad mailing list.

Further reading

See this guide for general information on writing a good bug report. If you need help with debugging a problem, see DebuggingProcedures.

取自“https://wiki.ubuntu.org.cn/index.php?title=UbuntuHelp:ReportingBugs&oldid=79463”