** Description changed:

  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 
(http://www.errors.ubuntu.com/user/ + printf $(sudo cat 
/sys/class/dmi/id/product_uuid) | sha512sum)
+ 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.

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

Title:
  whoopsie should not send some data to daisy

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to