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

Tue May 29 22:05:39 UTC 2018

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=308&rev2=309

Comment:
1) RM gksu as EOL. 2) MV'd+merge crash sects in Tips to earlier crash sect. as overlap. 3) As per LP#1773850 reworked crash sect's to streamline & add missing scenarios. 4) Misc. small fixes.

   * '''Proposing features and ideas:''' You should submit your idea to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list.
   * '''Filing a bug against a package not provided by the default, supported Ubuntu repositories:''' This is due to how it wasn't confirmed by Ubuntu Developers for your release. Problems that unsupported software have caused are upgrade issues, and the program or operating system not functioning correctly. Typically, what isn't supported is software from a PPA (Personal Package Archive), 3rd party packages, self-compiled software, etc. For more on supported Ubuntu repositories, please see [[https://help.ubuntu.com/community/Repositories|here]]. If you are using unsupported software, it is best to file a bug in that program's bug tracker directly. Instructions are generally available on the program maintainer's web site.
  
- /!\ If you want to file a translation or misspelling bug, follow the instructions [[#translation|here]].
- 
  == Perform a survey of your problem ==
  
  First, check the release notes of your supported version of Ubuntu for any known issues from [[https://wiki.ubuntu.com/Releases|here]].
  Second, check Launchpad for any duplicates, and make note of this.
  
+ /!\ If you want to file a translation or misspelling bug, follow the instructions [[#translation|here]].
+ 
+ == Reporting a crash ==
+ 
+ If an application crashes, what typically happens is [[https://wiki.ubuntu.com/Apport|Apport]] will display a window noting it is collecting information about the crash:
+ ||<style="border: 1px solid black">{{attachment:apport-1.png}}||
+ 
+ Once done, it will ask you if you would like to report it.
+ 
+ /!\ Before continuing, make sure the package [[https://launchpad.net/ubuntu/+source/whoopsie|whoopsie]] is installed. Otherwise, Apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of [[https://launchpad.net/ubuntu/+source/ubuntu-meta|ubuntu-desktop]], but for users of alternative desktops, or for server users, whoopsie has to be installed manually with apt-get install whoopsie. See bug #1001630 for details.
+ 
+ Once you report the crash, what happens next is dependent on what release you are using.
+ 
- == Reporting an application crash in the development release ==
+ === Reporting crash in the development release ===
  
- Please report an application crash via the methods outlined below and at [[https://wiki.ubuntu.com/DebuggingProgramCrash]].
+ What happens next is a web browser opens requesting you to login, and subsequently create a bug report on Launchpad. This report is automatically processed by [[Apport Retracing Service]], in order to provide developers with debugging information that makes it easier to fix the problem.
  
- If an application crashes, and you're using a development release, Apport should start automatically, raising an appropriate bug report for you to complete in Launchpad. This report is subsequently processed by [[Apport Retracing Service]], in order to provide developers with debugging information that make it easier to fix the problem.
- 
- == Reporting an application crash in the stable release ==
+ === Reporting a crash in the stable release ===
  
- Apport may come disabled by default. To enable it, edit the file:
- {{{
- /etc/default/apport
- }}}
- 
- and change:
- {{{
- enabled=0
- }}}
- 
- to:
- {{{
- enabled=1
- }}}
- 
- /!\ Even when enabled, apport will not upload crash reports to Launchpad for a stable release (see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. To file a report on Launchpad anyway, one may open the following file via a command line: {{{
+ By default, Apport will not upload crash reports to Launchpad for a stable release (see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]].
+ 
+ If you have a need to file a report on Launchpad anyways (e.g. you don't have access to the errors infrastructure, you want to subscribe others to a report to review it, etc.) one may do so by editing: {{{
- gksudo gedit /etc/apport/crashdb.conf
+ /etc/apport/crashdb.conf
  }}} and change: {{{
  'problem_types': ['Bug', 'Package'],
  }}} to: {{{
  # 'problem_types': ['Bug', 'Package'],
  }}}
- Save, close, and try to file the crash report again via: {{{
+ Save, close, and file the crash report via: {{{
- ubuntu-bug /var/crash/_my_crash_report.crash
+ ubuntu-bug /var/crash/FILENAME.crash
  }}}
  
- /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details.
+ === Reporting a crash when no message shows up and crash files created ===
  
- [[#Top|Back to top]]
+ Sometimes, Apport creates a crash file, but doesn't display a message asking to make a report about it. In this case, one may file a crash report via a terminal:{{{
+ ubuntu-bug /var/crash/FILENAME.crash
+ }}} Where FILENAME is the file name of the crash file you want to report.
  
- == Reporting a system crash ==
+ To confirm it was reported successfully in the stable release, the following files exist: {{{
+ /var/crash/FILENAME.upload
+ /var/crash/FILENAME.uploaded
+ }}}
  
- If your system locks up, freezes, logs you out, etc., then this is not an application crash, but a system crash. Please see below, and consult the following article for these types of problems [[https://help.ubuntu.com/community/DebuggingSystemCrash]].
+ === Reporting a crash when no message shows up and crash files not created ===
+ 
+ Sometimes, Apport isn't able to create crash files about the crash. If this is due to Apport being disabled one may edit the file: {{{
+ /etc/default/apport
+ }}} and change:
+ {{{
+ enabled=0
+ }}} to:
+ {{{
+ enabled=1
+ }}} If Apport is enabled, then you may have one of the following issues:
+  * For system crashes (e.g. system locks up, freezes, logs you out, etc.) one my gather debugging information about [[https://help.ubuntu.com/community/DebuggingSystemCrash|system crashes]].
+  * For application crashes (e.g. GUI application crash) one will have to manually capture the crash details following [[https://wiki.ubuntu.com/DebuggingProgramCrash|this article]].
+ 
+ [[#Top|Back to top]]
  
  == Reporting non-crash hardware and desktop application bugs ==
  
@@ -190, +205 @@

  
  You will need to answer a few questions, and a web browser will be launched to complete the bug report. Please do not attach the `.apport` or `.crash` file to the report, as this is not the same as performing the above mentioned steps.
  
- == Filing bugs at Launchpad.net ==
+ == Filing bugs manually at Launchpad.net ==
  
  If for some reason you cannot file a bug using the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpad's own bug report form]]. When doing so it is best if you have determined which package it should be filed against. Read '[[http://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]' for guidance or use [[ http://launchpad.net/ubuntu/ | Launchpad's package search feature ]]. We don't recommend this method for most bug reports because they will likely be missing crucial information, use ubuntu-bug if you can!
  
@@ -200, +215 @@

  
  where PACKAGENAME is the name of the source package about which you want to file the bug report.  
  
- In the event that you want to request a piece of software be packaged for Ubuntu please follow the instructions in the [[ https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu | wiki ]].
+ In the event that you want to request a piece of software be packaged for Ubuntu please follow the instructions in the [[https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu|wiki]].
- 
- == Crashes ==
- 
- If an application crashes, [[https://wiki.ubuntu.com/Apport|Apport]] will start automatically, raising an appropriate bug report for you to complete in Launchpad.  This provides developers with rich debugging information that will make it easier to fix the problem.
- 
- ||<style="border: 1px solid black">{{attachment:apport-1.png}}||
- 
  
  == Error: The launchpadlib Python module is not installed ==
  
@@ -218, +226 @@

  sudo apt-get -y install python-launchpadlib
  }}}
  
- === Package libreoffice not installed and no hook available, ignoring ===
+ == Package libreoffice not installed and no hook available, ignoring ==
  
  If one attempts to apport-collect and gets the error message: {{{
  Package libreoffice not installed and no hook available, ignoring
@@ -226, +234 @@

  sudo apt-get -y install libreoffice
  }}}
  
- === Crash reports ===
- 
- If your attachment is a crash report (ex. found in directory /var/crash), please do not attach it to an existing report. Instead, file a new report via a terminal so that [[https://help.ubuntu.com/community/ApportRetracingService|Apport Retracing Service]] may process it:
- {{{
- ubuntu-bug my_crash_report.crash
- }}}
- 
- === Non-crash userspace bugs ===
+ == Non-crash userspace bugs ==
  
  Sometimes it is useful to take a picture (with a camera or via PrtSc button), or [[https://help.ubuntu.com/community/Screencast|screencast]] of the problem to demonstrate how you reproduced it, what the bug specifically shows, and the impact it has.
  

