whoopsie id is not unique

[Jean-Baptiste Lallement]

The list of reports for a system actually includes reports for several different systems:

For example in this report:
https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766
the system has been installed on 2018-01-12 (user is mickymouse)

when you open the list of reports for this system
https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590

there are several reports which pre-dates the installation. Selecting other reports in the list show different systems. For example this report is from another system:
https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11

whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then falls back to other things.

It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus value e.g.

00020003-0004-0005-0006-000700080009

As seen in http://launchpad.net/bugs/1323081.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: whoopsie 0.2.58
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CrashReports: 640:1000:114:1986326:2018-01-25 09:03:26.946560382 +0100:2018-01-25 09:03:27.946560382 +0100:/var/crash/_usr_bin_gnome-calculator.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 11:44:49 2018
InstallationDate: Installed on 2013-09-03 (1604 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian Murray (brian-murray)]

On Thu, Jan 25, 2018 at 10:52:53AM -0000, Jean-Baptiste Lallement wrote:
> Public bug reported:
>
> The list of reports for a system actually includes reports for several
> different systems:
>
> For example in this report:
> https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766
> the system has been installed on 2018-01-12 (user is mickymouse)
>
> when you open the list of reports for this system
> https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590
>
> there are several reports which pre-dates the installation. Selecting other reports in the list show different systems. For example this report is from another system:
> https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11

I'm not convinced that these are not in fact the same system.
Unfortunately, the crashes are not complete apport reports and are
missing information that would help distinguish them as different
systems. However, as you mention whoopsie first tries to use
/sys/class/dmi/id/product and if the system were reinstalled this would
be the same. So its possible the owner of the system just reinstalled.
Additionally, looking at the crash reports we can see the installation
date is the same for one set of them and another set (the two oldest
crash reports), so I'm pretty certain this is a reinstall.

> whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then
> falls back to other things.
>
> It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus value
> e.g.
>
> 00020003-0004-0005-0006-000700080009
>
> As seen in http://launchpad.net/bugs/1323081.

I agree that this is a problem and I think its better tracked in bug
1636954. Although it is curious that the hashed system id for the bogus
product_uuid doesn't have many recent crashes. So, I wonder how wide
spread of a problem it is.

--
Brian Murray