bdmurray@upgrade-trusty-amd64:~$ grep whoopsie /var/log/syslog
Aug 24 12:04:55 upgrade-trusty-amd64 whoopsie[4310]: whoopsie 0.2.24.6ubuntu3 
starting up.
Aug 24 12:04:55 upgrade-trusty-amd64 whoopsie[4310]: Using lock path: 
/var/lock/whoopsie/lock
Aug 24 12:07:46 upgrade-trusty-amd64 whoopsie[4311]: Parsing 
/var/crash/_usr_bin_update-manager.1000.crash.
Aug 24 12:07:46 upgrade-trusty-amd64 whoopsie[4311]: Uploading 
/var/crash/_usr_bin_update-manager.1000.crash.
Aug 24 12:07:48 upgrade-trusty-amd64 whoopsie[4311]: Sent; server replied with: 
No error
Aug 24 12:07:48 upgrade-trusty-amd64 whoopsie[4311]: Response code: 200
Aug 24 12:07:48 upgrade-trusty-amd64 whoopsie[4311]: Reported OOPS ID 
0b455ae8-6a2e-11e6-a26a-fa163e30221b
Aug 24 12:08:11 upgrade-trusty-amd64 whoopsie[4311]: Sent; server replied with: 
No error
Aug 24 12:08:11 upgrade-trusty-amd64 whoopsie[4311]: Response code: 200

https://errors.ubuntu.com/oops/0b455ae8-6a2e-11e6-a26a-fa163e30221b

That OOPS contains GSettingsChanges, setting to verification-done.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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/1616559

Title:
  whoopsie should send more data to the Error Tracker

Status in whoopsie package in Ubuntu:
  Invalid
Status in whoopsie source package in Trusty:
  Fix Committed

Bug description:
  The whoopsie change which allows sending of any field less than 1 KB
  and creates a blacklist of not sent fields should be backported to
  Trusty.

  Test Case
  ---------
  1) launch update-manager
  2) kill -11 the update-manager process
  3) locate the update-manager .crash file and observe GsettingsChanges in it
  4) send crash report to Error Tracker (look for .uploaded file)
  5) view crash report in Error Tracker (find OOPS ID by looking at syslog / 
whoopsie status)
  6) observe GsettingsChanges not in it

  With the version of the package from -proposed GsettingsChanges should
  appear on the OOPS page for the crash that was sent.  An example can
  be found at https://errors.ubuntu.com/oops/a33cc22e-699c-11e6-909a-
  fa163eec78fa

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to