touch-packages team mailing list archive

[Chris J Arges <1382233@xxxxxxxxxxxxxxxxxx>]

Hello Brian, or anyone else affected,

Accepted whoopsie into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/whoopsie/0.2.24.6ubuntu2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: whoopsie (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: whoopsie (Ubuntu Vivid)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1382233

Title:
  whoopsie does not upload UnreportableReason field in crash reports

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Precise:
  In Progress
Status in whoopsie source package in Trusty:
  Fix Committed
Status in whoopsie source package in Vivid:
  Fix Committed
Status in whoopsie source package in Wily:
  Fix Committed

Bug description:
  Test Case
  ---------
  1) Edit a .crash file to have an UnreportableReason key and value e.g.
     UnreportableReason: Your system is weird.
  2) sudo service whoopsie stop
  3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
     sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com APPORT_REPORT_DIR=/var/crash/ whoopsie -f
  4) Put said .crash file in /var/crash/
  5) Put a corresponding .upload file in /var/crash/
  6) Observe whoopsie uploading the .crash file from the whoopsie log
     [16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
  7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
  8) verify the UnreportableReason appears there e.g.:
     https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8

  
  In src/whoopsie.c we can see the following:

      /* We would only want this to see how many bugs would otherwise go
       * unreported: */
      "UnreportableReason",

  The comment isn't exactly true.  apport uses the UnreportableReason
  key to include the following information:

    "You have some obsolete package versions installed."

  It'd be useful if this information was sent to the Error Tracker so
  that we can decide not to ask for a core dump from these crash
  reports. The "obsolete package versions" check is done by checking to
  see if the most recent available version of the package is installed,
  so if someone does not have -updates enabled then that pocket is not
  checked and "obsolete package versions" will not be present. This is
  desirable because the retracers will check to see if the package
  version is available from any pocket.

  So if we send UnreportableReason to the Error Tracker we can stop
  asking for core dumps and retracing crashes that will fail to retrace.

  However, the value for UnreportableReason is translated so this may
  not end up helping much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1382233/+subscriptions