Comment 16 for bug 1323081

I've been looking into this, and I think I have an idea what the problem is. (It's not related to *this* bug report though):

I think the whoopsie-id is *supposed* to be unique to each machine, but it's generated from the system UUID retrieved from the PC's BIOS (which in turn is *supposed* to be unique).

When I retrieve my system UUID, I get this:

$sudo dmidecode -s system-uuid
00020003-0004-0005-0006-000700080009

... which is a very suspicious value for a UUID!

Putting that number into Google reveals that this has caused problems with many other systems too. I'm guessing it's a dummy value that's produced when the BIOS manufacturer didn't do their job right.

I'd put money on you having the same UUID value if you run the above command.

So, it looks like what's happening here is that a number of different Ubuntu installations have been submitting crashes to errors.ubuntu.com under the same ID, which is why we're all seeing an unexpectedly large list of reports when we click "Show Previous Reports".

Furthermore, I wouldn't be surprised to find that the logging software on errors.ubuntu.com is filtering out some of those reports because other information provided in the crash logs reveals them to be inconsistent with each other. Because there are crash reports that I *know* I've submitted that don't appear in that list.