Reporting bugs

Differences between revisions 3 and 32 (spanning 29 versions)
⇤ ← Revision 3 as of 2017-04-25 05:44:54 →
Size: 925
Editor: es20490446e
Comment:
← Revision 32 as of 2017-05-28 03:38:52 → ⇥
Size: 3191
Editor: es20490446e
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Determine if the bug is really a bug == # CategoryDrafts


== Etiquette ==

 * Keep in mind that many software in Ubuntu is '''maintained''' by people in their spare time, brought to you for free.

 * If you care about an '''Ubuntu release''' not having bugs, test the [[http://cdimage.ubuntu.com/|daily image]] five months before [[https://wiki.ubuntu.com/Releases#Future|launch]]. So developers have time to fix it.

 * If '''writing more''' doesn't make a tangible difference, write less.

 * If you have any '''doubt''', you can [[mailto: Ubuntu Quality Team <ubuntu-quality@lists.ubuntu.com>|ask]] any time.


== Not bugs ==
Line 5: Line 19:
 * [[https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages|Requesting new software]]  * [[https://help.ubuntu.com/community/BIOSUpdate|Using a BIOS or firmware which can be causing the problem]]
Line 8: Line 22:

 * [[https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages|Requesting new software]]
Line 12: Line 28:

 * [[https://translations.launchpad.net/ubuntu|Reporting misspells]]
Line 23: Line 41:
1. Using the '''Synaptic application''' and the [[https://wiki.ubuntu.com/Bugs/FindRightPackage|list of common packages]], determine which one is the most likely to be affected. 1. Using the [[apt://synaptic|Synaptic]] application and the [[https://wiki.ubuntu.com/Bugs/FindRightPackage|list of common packages]], determine which software package is the most likely to be affected.
Line 25: Line 43:
2. In the '''Terminal''' application enter: 2. In the '''Terminal''' application enter the following, substituting PACKAGE with your package name:
Line 27: Line 45:
 ||ubuntu-bug package||  ||ubuntu-bug PACKAGE||
Line 32: Line 50:


== Reporting offline systems ==

If the system internet does't work, do the following:

1. On the '''target system''', in the Terminal application enter the following. Substituting PACKAGE with your package name:

 * For a crash:
 ||apport-cli -p PACKAGE --save bug.crash||
 * For a any other issue:
 ||apport-cli -f -p PACKAGE --save bug.apport||

2. '''Copy''' the generated file to the system used for filing the report.

3. On that '''reporting system''', in the Terminal application enter the following. Substituting FILE with your file name:

 ||ubuntu-bug -c FILE||


== Reporting unusable systems ==

Only if you system '''doesn't fit''' any of the above methods go to the following site, substituting PACKAGE with your package name:

 ||`https://bugs.launchpad.net/ubuntu/+source/PACKAGE/+filebug`||

Or if you '''haven't been able to determine the package''':

 ||`https://bugs.launchpad.net/ubuntu/+filebug`||


== ==

[[https://commons.wikimedia.org/wiki/File:Blueprint_of_Victory_-_Avoid_the_Black_Widow_of_war_production_-_NARA_534556_-_Without_Swastika.jpg|{{https://upload.wikimedia.org/wikipedia/commons/thumb/c/c0/Blueprint_of_Victory_-_Avoid_the_Black_Widow_of_war_production_-_NARA_534556_-_Without_Swastika.jpg/1024px-Blueprint_of_Victory_-_Avoid_the_Black_Widow_of_war_production_-_NARA_534556_-_Without_Swastika.jpg|(CC-BY-SA 4.0) 2017 Alberto Salvia Novella|height=450}}]]

Etiquette

  • Keep in mind that many software in Ubuntu is maintained by people in their spare time, brought to you for free.

  • If you care about an Ubuntu release not having bugs, test the daily image five months before launch. So developers have time to fix it.

  • If writing more doesn't make a tangible difference, write less.

  • If you have any doubt, you can ask any time.

Not bugs

You shouldn't file a bug here if you are:

Reporting windowed applications

In the Terminal application enter:

  • ubuntu-bug -w

Reporting non windowed applications

1. Using the Synaptic application and the list of common packages, determine which software package is the most likely to be affected.

2. In the Terminal application enter the following, substituting PACKAGE with your package name:

  • ubuntu-bug PACKAGE

3. Or if you haven't been able to determine the package, just enter:

  • ubuntu-bug

Reporting offline systems

If the system internet does't work, do the following:

1. On the target system, in the Terminal application enter the following. Substituting PACKAGE with your package name:

  • For a crash:

    apport-cli -p PACKAGE --save bug.crash
  • For a any other issue:

    apport-cli -f -p PACKAGE --save bug.apport

2. Copy the generated file to the system used for filing the report.

3. On that reporting system, in the Terminal application enter the following. Substituting FILE with your file name:

  • ubuntu-bug -c FILE

Reporting unusable systems

Only if you system doesn't fit any of the above methods go to the following site, substituting PACKAGE with your package name:

  • https://bugs.launchpad.net/ubuntu/+source/PACKAGE/+filebug

Or if you haven't been able to determine the package:

  • https://bugs.launchpad.net/ubuntu/+filebug

(CC-BY-SA 4.0) 2017 Alberto Salvia Novella

es20490446e/Reporting bugs (last edited 2017-05-28 03:38:52 by es20490446e)