Apport should still send reports to daisy.ubuntu.com for binaries in the blacklist

Bug #1064395 reported by Evan on 2012-10-09
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Undecided
Unassigned

Bug Description

Apport refuses to send crash reports for the packages responsible for binaries in the blacklist (/etc/apport/blacklist.d). This makes sense; Mozilla is much more capable of fixing problems in Firefox than we will ever be, and involving Launchpad creates an unnecessary middle-man.

However, for statistical purposes, it would still be wise to send these to daisy.ubuntu.com. This will let us understand just how well Mozilla is addressing these issues relative to the rest of the software in Ubuntu.

<https://wiki.ubuntu.com/ErrorTracker/BreakpadApplicationSupport>

Matthew Paul Thomas (mpt) wrote :

The difficulty here is how to let people choose whether to send the error report. If we put up Ubuntu's usual error alert, that would mean there were two error alerts in succession, Mozilla's and ours. I think there should be just one, but that confirming submission in it should send the report to both places.

Mozilla's error alert is more tailored to them, because it includes a comment field, easy inclusion of the URL you were on, and the ability to be notified of updates. So I think we should patch their crash dialog to send reports to us too.

Evan (ev) on 2012-11-01
tags: added: whoopsie-daisy
Evan (ev) wrote :

Matthew, should we change the Firefox crash reporter UI in any way? Perhaps to mention that the report will also be sent to Canonical?

Matthew Paul Thomas (mpt) wrote :

I think just change the checkbox text to ours, "Send an error report to help fix this problem". That avoids implying that Mozilla will be the only recipient.

This is an example of a change that should be flagged as affecting cross-release comparisons. <https://wiki.ubuntu.com/ErrorTracker#comparisons>

description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers