BugReporting

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2014-07-15 17:07:34 →
Size: 11730
Editor: adsl-74-179-123-212
Comment:
← Revision 2 as of 2014-07-15 17:08:55 → ⇥
Size: 8716
Editor: adsl-74-179-123-212
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
= Reporting a bug for ubuntu touch= = Reporting a bug for ubuntu touch =
Line 9: Line 9:
File against the ubuntu source package for the failed component. [[https://wiki.ubuntu.com/QATeam/TouchTesting/BugFiling|See this page]] for a full broken out list of components. File against the ubuntu source package for the failed component. [[QATeam/TouchTesting/BugFiling|See this page]] for a full broken out list of components.
Line 63: Line 63:
That's it, thanks for helping make ubuntu better! For reference, here are a couple examples showing reporting a bug and a crash.

==== Example output for bug report ====
Here's an example showing reporting a bug for the dialer-app from the phablet device.

{{{
$ ubuntu-bug dialer-app

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
........................................................................................
182 KB/s (14785 bytes in 0.078s)

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (14.1 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.

98%

*** To continue, you must visit the following URL:

  https://bugs.launchpad.net/ubuntu/+source/dialer-app/+filebug/59dbaa1c-2162-11e3-a3d4-d485646cd9a4?

You can launch a browser now, or copy this URL into a browser on another computer.


Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): C
}}}

==== Example output for crash report ====
Here's an example showing reporting a crash from the phablet device.

{{{
phablet@ubuntu-phablet:~$ apport-cli /var/crash/_sbin_init.32011.crash

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (7.8 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
........................................==== AUTHENTICATING FOR com.ubuntu.apport.root-info ===
Authentication is required to collect system information for this problem report
Authenticating as: phablet,,, (phablet)
Password: ....................................................................................

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.

98%

*** To continue, you must visit the following URL:

  https://bugs.launchpad.net/ubuntu/+source/sbin-app/+filebug/47dbaa1c-2162-11e3-a3d4-d485246cd9a4?

You can launch a browser now, or copy this URL into a browser on another computer.


Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): C

}}}		 That's it, thanks for helping make ubuntu better!


Reporting a bug for ubuntu touch

All bugs filed should use the avengers tag. Please ensure you add the 'avengers' tag when filing. If you think the bug you are reporting is a good candidate for an automated test to prevent future regressions, you may also add touch-needs-autopilot to the bug.

What package should I file against?

File against the ubuntu source package for the failed component. See this page for a full broken out list of components.

Filing the Bug

To file a bug, it's easiest to connect your device to a pc.

Connect your device to the pc via a usb cable. Next, shell into the device by typing phablet-shell. If you need to, install the phablet-tools package so this command is availible to you. 

$ phablet-shell

Check for the existence of a crash file in /var/crashes. If the crash file matches the date and time of the issue you experience, you can use the crash file to file the bug as it contains information useful to a developer. If there is no crash file, continue to file the bug using ubuntu-bug. 

$ ls -al /var/crash

Using ubuntu-bug

Since there is no crash file, you need to determine the package that is misbehaving. You will need the package name of the package in order to file. Unsure of which package?

While still shelled into the device, run the ubuntu-bug command, specifying the package name as the argument. 

$ ubuntu-bug PACKAGE_NAME

Now, continue filing the bug via launchpad.

Filing with a crash file in /var/crash

If the bug is a crash and there is a crash file in /var/crash, you can report it with apport.

From a shell on the device, run the follow apport command: 

  $ apport-cli /var/crash/name_of_crash_file.crash

Apport will read the crash file and process it. Follow the instructions as prompted. When you are asked, "What would you like to do?", enter 's' to send the report.

Now, continue filing the bug via launchpad.

Finishing the bug report

Apport will upload the report, and display a URL, looking similar to this 

*** To continue, you must visit the following URL:

  https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+filebug/<UUID>

If prompted, you may safely enter 'c' to cancel launching a browser on the device.

Instead, copy and paste the link from the terminal into a browser window on your pc for easier report entry. The browser will launch and display a ready to file bug report. Finish filling in the description of the issue. When filing, make sure you include the steps needed for others to reproduce the issue, and what the result was versus what you expected the result to be. If you are reporting a crash, mention what you were doing on the device when the crash occurred. This is important to ensure the bug is able to be reproduced, and ultimately fixed.

That's it, thanks for helping make ubuntu better!

Triaging

Once bugs have been filed they need to be confirmed, and ideally, have a defined scenario for recreating in order for developers to fix them. To help with triaging, simply read a bug report from the list below and try it on the latest build for your device. If you can recreate it, mark the bug status as confirmed.

Needs work

Completed work

List of all reported Bugs

Tags

Tags are used to keep handy lists of the work being done. It lets us see the status of bugs and testcase automation.

What does each tag mean?

Tag

Description

avengers

Used for filing bugs found during exploratory testing of ubuntu touch images

touch-needs-autopilot

Used to tag bugs that are candidates for automation to prevent recurrence once fixed

qa-touch-automated

Used to tag bugs that are being automated with autopilot

QATeam/TouchTesting/BugReporting (last edited 2015-10-26 11:26:31 by dholbach)