Launchpad spam discourages bug reporting

[Mark Lord]

When reporting (K)Ubuntu bugs, they frequently get reported multiple times, and somebody (Ubuntu) merges the duplicates. Once this happens, the original reporters get included on the mailing lists for *all* duplicates, which can number in the dozens.

There is no way to "unsubscribe" from the subsequent 10 emails-a-day that results from this, because there is no way to know which original bug was the one that put us on the merged spam list.

If this doesn't get fixed (and soon!), then I'm not going to report any further bugs, and I suspect the same applies to lots of other recently abused testers/reporters.

Thanks.

[Dennis Kaarsemaker (dennis)]

Not a bug in ubuntu, and you can simpy click the unsubscribe link... (i think, never needed it - if you can't open a new task on this bug against the launchpad upstream product)

[Mark Lord (launchpad-rtr)]

>you can simpy click the unsubscribe link...

WRONG. The duplicate bugs don't have an "unsubscribe link" to click on -- only the original bug has that.. whichever one of the thirty or so it was.

I guess I'll have to create a new launchpad ID and unique email address for each bug report from now on, and then delete the email ID immediately to avoid the spam from the inevitable dups.

Either that or just start emailing Ubuntu maintainers directly instead of using Launchpad.. yes, that's what I'll do.

[Mark Lord (launchpad-rtr)]

This is the new method Ubuntu has chosen, so this *is* now an Ubuntu bug.

The duplicate bugs don't present an "unsubscribe" link.

If you really want us to help test and report bugs, then you've got to make the system work.

-ml

[Dennis Kaarsemaker (dennis)]

Again, this is NOT a bug in ubuntu, but in launchpad.

[Christian Reis (kiko)]

Yeah, good point. We should make it easy to actually unsubscribe in this situation.

[Manuel López-Ibáñez (manuellopezibanez)]

I would vote for changing the title and description of this bug. It is far too temperamental and does not give any clear information on what the bug is about. I would, modestly, propose something more similar to bug 48860.