Launchpad bug stats disconnected from reality (errors.ubuntu.com)

Bug #1018688 reported by Daniel van Vugt
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Apport
Won't Fix
Undecided
Unassigned

Bug Description

I suspect Launchpad is dangerously disconnected from reality when it comes to number of people affected by a bug.

Examples:

Bug 956515:
Launchpad says: Affects 1 person, 0 duplicates.
errors.ubuntu.com says: It was reported 358 times in the past month.

Bug 901211 (duplicate of bug 833729):
Launchpad says: Affects 37 people, but the fix is released and no duplicates since February.
errors.ubuntu.com says: It was reported 2025 times in the past month (June).

This is very worrying. Developers won't have a clue as to what is actually the hottest bug if it's not showing up in Launchpad.

Revision history for this message
William Grant (wgrant) wrote :

Launchpad only knows what it's told. If errors.ubuntu.com is collecting the data and not telling Launchpad, that's not really a Launchpad problem.

no longer affects: launchpad
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I logged the bug against launchpad because it probably needs enhancement. Something like supporting anonymous votes for a bug from apport. Or showing "number of occurrences in the past 30 days".

If we ignore the numbers from people who either don't have launchpad accounts, or can't be bothered reporting bugs, then I think we're ignoring the vast majority of users.

Revision history for this message
Martin Pitt (pitti) wrote :

There is not much we can do about it as long as we have two places to report bugs. And for development releases we really do want Launchpad bugs, as they are so much more actionable than errors.u.c.

The LP numbers are actually correct, but only in the context of "in Launchpad" of course. No error tracker in the world can know how many people are really affected by a bug. So if nothing else, there should be some wording adjustment in LP.

Changed in apport:
status: New → Won't Fix
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.