whoopsie should not send some data to daisy

Bug #1306175 reported by Brian Murray
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie (Ubuntu)
Fix Released
High
Brian Murray
Precise
Invalid
High
Brian Murray
Saucy
Fix Released
High
Brian Murray
Trusty
Fix Released
High
Brian Murray
whoopsie-daisy (Ubuntu)
Invalid
Undecided
Unassigned
Precise
Fix Released
Undecided
Unassigned
Saucy
Invalid
Undecided
Unassigned
Trusty
Invalid
Undecided
Unassigned

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.

tags: added: trusty
Changed in whoopsie (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in whoopsie (Ubuntu Trusty):
milestone: none → ubuntu-14.01
milestone: ubuntu-14.01 → none
description: updated
Changed in whoopsie (Ubuntu Trusty):
status: Triaged → In Progress
assignee: nobody → Brian Murray (brian-murray)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie - 0.2.24.5

---------------
whoopsie (0.2.24.5) trusty; urgency=medium

  * Do not send Stacktrace, and ThreadStacktrace as retracing with ddebs will
    provide more useful versions of them. (LP: #1306175)
 -- Brian Murray <email address hidden> Thu, 10 Apr 2014 10:58:39 -0700

Changed in whoopsie (Ubuntu Trusty):
status: In Progress → Fix Released
Changed in whoopsie (Ubuntu Precise):
status: New → Triaged
Changed in whoopsie (Ubuntu Saucy):
status: New → Triaged
Changed in whoopsie (Ubuntu Precise):
importance: Undecided → High
Changed in whoopsie (Ubuntu Saucy):
importance: Undecided → High
description: updated
Changed in whoopsie (Ubuntu Precise):
assignee: nobody → Brian Murray (brian-murray)
Changed in whoopsie (Ubuntu Saucy):
assignee: nobody → Brian Murray (brian-murray)
Changed in whoopsie (Ubuntu Precise):
status: Triaged → In Progress
Changed in whoopsie (Ubuntu Saucy):
status: Triaged → In Progress
tags: added: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote :

I've verified this fix for saucy; here is the error report from the system with the 0.2.24.1.2 version of whoopsie.

https://errors.ubuntu.com/oops/752f63b0-c4c5-11e3-9c4a-fa163e373683

There is no Stacktrace, nor ThreadStacktrace.

tags: added: verification-done-saucy
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

I've verified this fix for precise, you can find the error report from whoopsie version 0.1.34 here:

https://errors.ubuntu.com/oops/56555f16-c4d0-11e3-8bb1-fa163e707a72

There is no Stacktrace or ThreadStacktrace.

tags: added: verification-done-precise
removed: verification-needed
Changed in whoopsie (Ubuntu Precise):
status: In Progress → Fix Committed
Changed in whoopsie (Ubuntu Saucy):
status: In Progress → Fix Committed
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

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.

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
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie - 0.2.24.1.2

---------------
whoopsie (0.2.24.1.2) saucy; urgency=medium

  * Do not send Stacktrace, and ThreadStacktrace as retracing with ddebs will
    provide more useful versions of them. (LP: #1306175)
 -- Brian Murray <email address hidden> Mon, 14 Apr 2014 14:23:24 -0700

Changed in whoopsie (Ubuntu Saucy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie-daisy - 0.1.34

---------------
whoopsie-daisy (0.1.34) precise-proposed; urgency=medium

  * Do not send Stacktrace, and ThreadStacktrace as retracing with ddebs will
    provide more useful versions of them. (LP: #1306175)
 -- Brian Murray <email address hidden> Mon, 14 Apr 2014 15:48:06 -0700

Changed in whoopsie-daisy (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.