[Community Help Wiki] Update of "ReportingBugs" by penalvch

[Help Ubuntu]

Dear Wiki user,

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

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

Comment:
1) Added support note on headless system. 2) Re-worded intro paragraph to etiquette as it was out of place now that it's been moved.

  
  = Tips and tricks =
  
- == Filing bugs when off-line ==
+ == Filing bugs when offline or using a headless setup ==
  
- In the event that you have an issue with your Internet connection or want to file a bug for another system you can still do this using apport.  
+ In the event that you have an issue with your internet connection, want to file a bug for another system, or have trouble reporting from a headless setup, you can still do this using apport.  
  
  First, on the target system, gather the information in a file:
  
@@ -286, +286 @@

  [[#Top|Back to top]]
  
  
- = Getting advice =
- 
- Still have doubts about the bug report filing process? You can ask someone on [[irc://irc.freenode.net/#ubuntu-bugs|#ubuntu-bugs]] on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server or on the [[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|bugsquad mailing list]].
- 
- [[#Top|Back to top]]
- 
- 
  = Bug reporting etiquette =
  
+ Following bug reporting etiquette best presents your Launchpad report so that it gets addressed as soon as possible. As well, it minimizes unnecessary pain points for developers, triagers, and original reporters.
- Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. While this is targeted to the new bug reporter, experienced reporters would find these tips invaluable in getting their bugs looked at by a developer and ultimately fixed.
- 
  
  == All bug reports ==
  
@@ -305, +297 @@

   * '''Please do not complain because someone sent what one perceives to be a automated or "canned" response'''. <<BR>> If the response is asking you to do something that you have't done (ex. test the latest development release, file a new report, etc.) do it, as it would get you closer to having your bug fixed faster. Complaining about this is inconsiderate of the Ubuntu triagers and developers who are saving time in comparison to hand typing every single character in an e-mail that goes out their inbox.
   * '''Please test the latest version of the package that is considered responsible for the problem.''' <<BR>> For bugs in the [[https://launchpad.net/ubuntu/+source/linux|Linux (Ubuntu)]] package, unless the upstream maintainer or kernel developer notes otherwise, if a new mainline kernel comes out, and you haven't tested with it, you run the strong risk of it not being attended to upstream.
   * '''Please do not post comments such as “Me too!”, “+1”, “bump”, “same here”, etc.''', as it is largely unhelpful, produces spammy e-mail traffic to everyone subscribed to the report, and quite often turns out not to be the same root cause. Instead, please follow the below mentioned procedures.
-  * '''Please do not post URLs of requested information.''' <<BR>> For example, links to pastebin.com, paste.ubuntu.com, dropbox.com, etc. If a triager or developer asks you for some information on reproducing or testing, please do not make them dumpster dive by just posting a URL, or saying you already did something in some other report. Instead, put the full reproduction or testing results into the report itself, and if you have to, then post the link.
+  * '''Please do not post URLs of requested information.''' <<BR>> For example, links to pastebin.com, paste.ubuntu.com, dropbox.com, etc. If a triager or developer asks you for some information on reproducing or testing, please do not make them dumpster dive by just posting a URL, or saying you already did something in some other report. Instead, put the full reproduction or testing results into the report itself, uncompressed and untarred, and if you have to, then post the link.
   * '''Please do not stack multiple issues into one report'''. <<BR>> For example, jamming suspend and hibernate into one report, reporting multiple [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|hotkey]] problems into one report (ex. Fn+F3 doesn't turn off my laptop WiFi, Fn+Right doesn't turn the brightness on my [[https://wiki.ubuntu.com/Kernel/Debugging/Backlight|backlight]] down, my brightness settings are not remembered after reboot, etc.). Please make one report for each individual problem.
   * '''Please do not complain about how long it takes to fix a bug.''' <<BR>> This goes along with saying things like severity of your bug is high so it should be fixed immediately, “I cannot believe it’s not fixed…”, XYZ person(s) do not care about fixing bugs, etc. Especially, if you have not followed the directions mentioned in this article, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your e-mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
   * '''Please keep the bug report as objective as possible.''' <<BR>> It is desired for you to provide a fact based, technical impact statement on you, your environment, and the potential or actual impact on the community at large.
@@ -331, +323 @@

   * '''Please do not solicit non-original reporters to post comments, attachments, etc.'''
   * '''Please do not attach anything to another persons report.''' <<BR>> Adding undesired attachments when not asked by a triager or developer creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers.
  
+ = Getting advice =
+ 
+ Still have doubts about the bug report filing process? You can ask someone on [[irc://irc.freenode.net/#ubuntu-bugs|#ubuntu-bugs]] on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server or on the [[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|bugsquad mailing list]].
+ 
+ [[#Top|Back to top]]
  
  = Other languages =