“UbuntuHelp:ReportingBugs”的版本间的差异
来自Ubuntu中文
小 |
小 |
||
| 第8行： | 第8行： | ||
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. | 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. | ||
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=report-a-problem.png | https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=report-a-problem.png | ||
| − | Apport is available for Ubuntu | + | Apport is available for Ubuntu 7.04 (Feisty Fawn) and later versions. |
https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=filebug-shot.png | https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=filebug-shot.png | ||
=== Filing from the command line === | === Filing from the command line === | ||
| 第21行： | 第21行： | ||
ubuntu-bug linux</nowiki></pre> | ubuntu-bug linux</nowiki></pre> | ||
will file a bug on the Linux kernel. | will file a bug on the Linux kernel. | ||
| − | ==== Ubuntu | + | ==== Ubuntu 7.04 through 8.04 LTS ==== |
<pre><nowiki> | <pre><nowiki> | ||
apport-cli -f -p PACKAGE</nowiki></pre> | apport-cli -f -p PACKAGE</nowiki></pre> | ||
| 第33行： | 第33行： | ||
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. | 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. | 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. | + | 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. To add an attachment to the bug use the '''Include an attachment''' section of the bug form. Additional attachments, if necessary, can be added after the bug is reported via '''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. | 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 == | == When not to file a bug == | ||
| 第40行： | 第39行： | ||
* '''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. | * '''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 posted to http://brainstorm.ubuntu.com/ or discussed on the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss ubuntu-devel-discuss] mailing list. | * '''Development ideas''' should be posted to http://brainstorm.ubuntu.com/ or 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)]], [http://www.ubuntu.com/getubuntu/releasenotes/704 7.04 (Feisty Fawn)], [http://www.ubuntu.com/getubuntu/releasenotes/710 7.10 (Gutsy Gibbon)], [http://www.ubuntu.com/getubuntu/releasenotes/804 8.04 (Hardy Heron)]. If you have further information about an already reported bug, add this information to the existing reported bug, instead of opening a new one. | + | * '''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)]], [http://www.ubuntu.com/getubuntu/releasenotes/704 7.04 (Feisty Fawn)], [http://www.ubuntu.com/getubuntu/releasenotes/710 7.10 (Gutsy Gibbon)], [http://www.ubuntu.com/getubuntu/releasenotes/804 8.04 (Hardy Heron)], [http://www.ubuntu.com/getubuntu/releasenotes/810 8.10 (Intrepid Ibex)]. If you have further information about an already reported bug, add this information to the existing reported bug, instead of opening a new one. |
== Getting advice == | == 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]. | 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]. | ||
2008年12月16日 (二) 19:58的版本
 |
点击翻译: |
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.
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.
Apport is available for Ubuntu 7.04 (Feisty Fawn) and later versions.
Filing from the command line
Ubuntu Intrepid
ubuntu-bug PACKAGE
Lets you file a bug against a known package and automatically include all the useful debug information. Use
ubuntu-bug PID
If you want to file against a running program with a known Process ID (PID) (see System -> Administration -> System Monitor).
ubuntu-bug linux
will file a bug on the Linux kernel.
Ubuntu 7.04 through 8.04 LTS
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 (Ubuntu 6.06)
If for some reason you cannot file a bug through the Apport tool you can file one via Launchpad (Apport is available for Ubuntu 6.10 (Edgy Eft) and later versions.). 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. To add an attachment to the bug use the Include an attachment section of the bug form. Additional attachments, if necessary, can be added after the bug is reported via 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 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 (including suggestions to change defaults) should be discussed on the ubuntu-devel-discuss mailing list.
- Development ideas should be posted to http://brainstorm.ubuntu.com/ or discussed on the ubuntu-devel-discuss mailing list.
- Already filed - Please check if it has already been reported by searching through the existing bugs and the release notes for your release of Ubuntu 6.06|(Dapper Drake), 7.04 (Feisty Fawn), 7.10 (Gutsy Gibbon), 8.04 (Hardy Heron), 8.10 (Intrepid Ibex). If you have further information about an already reported bug, add this information to the existing reported bug, instead of opening a new one.
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.
