Public bug reported: 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 ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: Invalid ** Affects: whoopsie (Ubuntu Trusty) Importance: High Assignee: Brian Murray (brian-murray) Status: Triaged ** Tags: trusty ** Changed in: whoopsie (Ubuntu) Status: New => Triaged ** Also affects: whoopsie (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu) Status: Triaged => Invalid ** Changed in: whoopsie (Ubuntu Trusty) Status: New => Triaged ** Changed in: whoopsie (Ubuntu Trusty) Importance: Undecided => High ** Summary changed: - whoopsie still uses acceptable fields to decide what to upload + whoopsie should send more data to the Error Tracker -- 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: Triaged 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
