[Bug 1616559] Re: whoopsie should send more data to the Error Tracker
Chris J Arges
1616559 at bugs.launchpad.net
Wed Aug 24 17:42:12 UTC 2016
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.6ubuntu3 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: Triaged => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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
More information about the foundations-bugs
mailing list