“UbuntuHelp:UbuntuStudio/ReportingBugs”的版本间的差异
来自Ubuntu中文
小 （新页面: {{From|https://help.ubuntu.com/community/UbuntuStudio/ReportingBugs}} {{Languages|UbuntuHelp:UbuntuStudio/ReportingBugs}} When you find a bug, help out the developers by filing a report a...） |
小 |
||
| （未显示同一用户的2个中间版本） | |||
| 第1行： | 第1行： | ||
{{From|https://help.ubuntu.com/community/UbuntuStudio/ReportingBugs}} | {{From|https://help.ubuntu.com/community/UbuntuStudio/ReportingBugs}} | ||
{{Languages|UbuntuHelp:UbuntuStudio/ReportingBugs}} | {{Languages|UbuntuHelp:UbuntuStudio/ReportingBugs}} | ||
| + | Always make sure it's a bug specific to Ubuntu Studio when filing. Otherwise a bug should be filed against the specific app where you are having trouble. | ||
When you find a bug, help out the developers by filing a report at the Ubuntu Studio [https://bugs.launchpad.net/ubuntustudio-project Launchpad Page]. | When you find a bug, help out the developers by filing a report at the Ubuntu Studio [https://bugs.launchpad.net/ubuntustudio-project Launchpad Page]. | ||
| − | |||
== What to Include in the Bug Report == | == What to Include in the Bug Report == | ||
When reporting a bug in Ubuntu Studio, please include the following: | When reporting a bug in Ubuntu Studio, please include the following: | ||
| − | * System specifications. | + | * System specifications. ie: |
| + | * kernel | ||
| + | * CPU | ||
| + | * Amount of RAM | ||
* Steps to recreate the bug. | * Steps to recreate the bug. | ||
After the initial assessment of the bug, you may be asked more detailed information. Please be prompt in providing this information, as it will help developers in quickly diagnosing the problem. | After the initial assessment of the bug, you may be asked more detailed information. Please be prompt in providing this information, as it will help developers in quickly diagnosing the problem. | ||
| − | |||
== What Not to Include in a Bug Report == | == What Not to Include in a Bug Report == | ||
* An Ambiguous Title - Please make the title of the bug report specific. | * An Ambiguous Title - Please make the title of the bug report specific. | ||
* A Laundry List - Do not include a list of all the bugs you have run into while using Ubuntu Studio, file a separate bug report for each bug. | * A Laundry List - Do not include a list of all the bugs you have run into while using Ubuntu Studio, file a separate bug report for each bug. | ||
| − | |||
== Additional Resources == | == Additional Resources == | ||
* [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] - A detailed guide in providing an effective bug report. | * [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] - A detailed guide in providing an effective bug report. | ||
| − | * [[UbuntuWiki | + | * [[UbuntuWiki:Backtrace|Creating a Backtrace]] - In some cases it may be necessary to provide a backtrace, which helps programmers find the specific location of a crash inside an application. |
[[category:UbuntuHelp]] | [[category:UbuntuHelp]] | ||
2008年10月20日 (一) 00:55的最新版本
 |
点击翻译: |
English |
请不要直接编辑翻译本页，本页将定期与来源同步。 |
Always make sure it's a bug specific to Ubuntu Studio when filing. Otherwise a bug should be filed against the specific app where you are having trouble. When you find a bug, help out the developers by filing a report at the Ubuntu Studio Launchpad Page.
What to Include in the Bug Report
When reporting a bug in Ubuntu Studio, please include the following:
- System specifications. ie:
- kernel
- CPU
- Amount of RAM
- Steps to recreate the bug.
After the initial assessment of the bug, you may be asked more detailed information. Please be prompt in providing this information, as it will help developers in quickly diagnosing the problem.
What Not to Include in a Bug Report
- An Ambiguous Title - Please make the title of the bug report specific.
- A Laundry List - Do not include a list of all the bugs you have run into while using Ubuntu Studio, file a separate bug report for each bug.
Additional Resources
- How to Report Bugs Effectively - A detailed guide in providing an effective bug report.
- Creating a Backtrace - In some cases it may be necessary to provide a backtrace, which helps programmers find the specific location of a crash inside an application.
