No bug mail generated at all for private reports

Bug #563988 reported by MarcRandolph
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: apport

Currently, the only way to determine that new crash (private) bugs have arrived is to visit the launchpad bug report for each individual Ubuntu package - no bug mail at all is generated. This might be fine if there were only a few packages to watch, but this does not scale to something like the Ubuntu project where there are thousands of packages. Many crashes are being ignored or not handled in a timely manner because those packages are not visited. Even if I am only interested a small number of packages, I dare say it is pretty close to unworkable (having to remember to go visit the bug reports for each package).

I understand the desire to minimize bug spam, but could the flow be changed to the following to allow for at least one bug mail to be sent per non-duplicate bug?

1. retrace
2. dup check
3. if not a duplicate, notify those users subscribed to that package, and who are able to see private reports, with a status (if nothing else, just let them see the duplicate-check tag be removed).

MarcRandolph (mrand)
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Right now a lot of developers explicitly do not want bug mails for crash reports (and their million duplicates, etc). We just have an escalation procedure once the 10th duplicate is reported, to get it on the QA team's radar. So this is pretty much "wontfix" in this general description.

However, for your particular use case of mythbuntu, the retracer could have a map to subscribe a particular team (in addition to ubuntu-bugcontrol) for particular packages.

So perhaps this should be reformulated for this more specific use case?

Revision history for this message
MarcRandolph (mrand) wrote : Re: [Bug 563988] Re: No bug mail generated at all for private reports

I understand and appreciate wanting to eliminate hundreds of
duplicates, but aren't we throwing the baby out with the bathwater?

I have no problem with squelching emails if/when duplicates show up,
but I think that one initial email is pretty important. As it is now,
you may not know for a long time (possibly never) that there is an
issue - after all, I would expect that when I subscribe to bug mail
for a package, I would get that bug mail (and I think the silent
majority of triagers would too).

I've made my case. If you still feel this is a WON'T FIX, I'll accept it.
As for the Mythbuntu project, we'll go with whatever Mario believes is needed.

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in apport (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apport (Ubuntu) because there has been no activity for 60 days.]

Changed in apport (Ubuntu):
status: Incomplete → Expired
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.