[Bug 1306175] Re: whoopsie should not send some data to daisy

Adam Conrad adconrad at 0c3.net
Fri Apr 18 15:16:52 UTC 2014


The verification of the Stable Release Update for whoopsie-daisy has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.

** Also affects: whoopsie-daisy (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: whoopsie-daisy (Ubuntu Saucy)
       Status: New => Invalid

** Changed in: whoopsie-daisy (Ubuntu Trusty)
       Status: New => Invalid

** Changed in: whoopsie (Ubuntu Precise)
       Status: Fix Committed => Invalid

** Changed in: whoopsie-daisy (Ubuntu Precise)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie-daisy in Ubuntu.
https://bugs.launchpad.net/bugs/1306175

Title:
  whoopsie should not send some data to daisy

Status in “whoopsie” package in Ubuntu:
  Fix Released
Status in “whoopsie-daisy” package in Ubuntu:
  Invalid
Status in “whoopsie” source package in Precise:
  Invalid
Status in “whoopsie-daisy” source package in Precise:
  Fix Released
Status in “whoopsie” source package in Saucy:
  Fix Released
Status in “whoopsie-daisy” source package in Saucy:
  Invalid
Status in “whoopsie” source package in Trusty:
  Fix Released
Status in “whoopsie-daisy” source package in Trusty:
  Invalid

Bug description:
  TEST CASE:
  0) sudo rm -f /var/crash/*
  1) run xeyes &
  2) then use 'pkill -11 xeyes'
  3) choose to send your crash to errors
  4) answer no to any additional data collection questions as its not used
  5) verify there is a _usr_bin_xeyes.1000.uploaded file in /var/crash (this means the crash was uploaded to errors)
  6) go to the crashes you've reported page at errors.ubuntu.com (echo "http://errors.ubuntu.com/user/"$(printf $(sudo cat /sys/class/dmi/id/product_uuid) | sha512sum) )
  7) click on the link for the top crash there (it is the one most recently reported)
  With the version of whoopsie from -proposed you will not find keys for Stacktrace or ThreadStacktrace on the page for the crash.

  REGRESSION POTENTIAL:
  None, really we are just uploading less data to the error tracker which wasn't used anyway.

  apport reports contain some incomplete data that becomes more useful
  when the crash report has been retraced with the package with debug
  symbols enabled, it is wasteful for whoopsie to be submitting this
  data to daisy.

  The fields are Stacktrace, and ThreadStacktrace.  These should be
  removed from whoopsie's acceptable_fields and not sent to daisy any
  longer.

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



More information about the foundations-bugs mailing list