[Community Ubuntu Documentation] Update of "ReportingBugs" by penalvch

[Help Ubuntu]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification.

The "ReportingBugs" page has been changed by penalvch:
http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=186&rev2=187

Comment:
Added details on improving bug reports throughout the article

   * Please provide all relevant information from [[https://wiki.ubuntu.com/DebuggingProcedures]] when you first report your bug. This is the number one reason why bugs do not get marked [[https://wiki.ubuntu.com/Bugs/Status|Triaged]], as the minimum requirements for dealing with the problem by a developer are not provided.
   * If a triager or developer asks you to provide information, please avoid arguing with them. Just provide the information as requested. If you have a strong disagreement with what a triager or developer is asking of you, please resolve it with them via personal message, instead of turning a bug development report into a "let's talk about talking about the problem" report. The Ubuntu community takes a favor to objective, technical discourse.
   * Many of the triagers and developers who are providing support to you, are volunteers doing so out of altruism. Please keep this in mind when making your comments.
-  * The high majority of [[https://launchpad.net/ubuntu/+source/linux|linux]] package, hardware, non-user space bugs are hardware dependent on both the hardware itself, and what it is connected to. The general rule of thumb is one report, per person, per hardware combination, per bug. For more on this please see below sections:
+  * The high majority of [[https://launchpad.net/ubuntu/+source/linux|linux]] package, hardware, non-user space bugs are hardware dependent on both the hardware itself, and what it is connected to. The rule of thumb is one report, per person, per hardware combination, per bug. For more on this please see below sections:
  [[https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported]]
  
  [[https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug]]
@@ -59, +59 @@

   * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 LTS (Precise Pangolin)]]
  
  If the problem is not in the package [[https://launchpad.net/ubuntu/+source/linux|linux]], and you have further information about an already reported bug, add this information to the existing report, rather than opening a new one.
+ If the problem is in the package [[https://launchpad.net/ubuntu/+source/linux|linux]], and you are the original reporter, here are the ways to maximize the speed with which your bug is fixed:
+  * Check for the problem in the earliest release that works for your hardware and the lastest. Report your testing results in the report.
+  * If your bug is a regression, commit bisect it following https://wiki.ubuntu.com/Kernel/KernelBisection . Report your bisect results in the report.
+  * Test for this problem in the mainline kernel following https://wiki.ubuntu.com/Kernel/MainlineBuilds . Report your mainline testing results in the report.
+  * Please do not assume because you have the same desktop or laptop model line as another original reporter's bug report, that your problem is the same. Frequently, computer vendors use different parts under the hood within the same model line.
  
+ === Sound, X drivers, Linux Kernel Bugs ===
+ 
- /!\ '''For sound, X drivers, and [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel bugs''': please open a '''new''' bug instead of adding debugging information, attachments, or "Me too!" comments on what may appear to be a similar bug: chances are that your hardware does not match the existing bug's hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug.
+ /!\ '''For sound, X drivers, and [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel bugs''': please open a '''new''' report instead of adding debugging information, attachments, apport-collect'ing, or "Me too!" comments on what may appear to be a similar bug: chances are that your hardware does not match the existing bug's hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug.
  
  [[#Top|Back to top]]