As part of (un)stable whoopsie persistent machine identifier generation /sys/class/dmi/id/product_uuid is used.
However:
$ ls /sys/class/dmi/id/product_uuid
-r-------- 1 root root 4096 Aug 2 01:23 /sys/class/dmi/id/product_uuid
It's not world-readable. Hence API calls to whoopsie_identifier_generate return different results for root and non-root users.
Either whoopsie should stop using product_uuid, or api calls to whoopsie_identifier_generate should be denied and instead one should use whoopsie-preferences which gets the full uuid...
As part of (un)stable whoopsie persistent machine identifier generation /sys/class/ dmi/id/ product_ uuid is used.
However: dmi/id/ product_ uuid dmi/id/ product_ uuid
$ ls /sys/class/
-r-------- 1 root root 4096 Aug 2 01:23 /sys/class/
It's not world-readable. Hence API calls to whoopsie_ identifier_ generate return different results for root and non-root users.
Either whoopsie should stop using product_uuid, or api calls to whoopsie_ identifier_ generate should be denied and instead one should use whoopsie- preferences which gets the full uuid...