I am not sure we got the root cause of the UUID problem.

Guille wrote:

> AAAANNNDDD! It looks I found the real cause of this!
>
> - I tested an image pre-new session manager, and an image post-new session manager. The issue only appeared in the latter.
>
> - Checking, it seems that UUIDGenerator is not subscribed to the new startup list. This means that the UUIDGenerator is not being reinitialized on every startup. This means, moreover, that every person that is loading the latest Pharo image is using the same UUIDGenerator instance, with the same random seed => same generated UUIDs.

Yes, that is correct. But ...

UUID new

ends up calling

UUID>>#primMakeUUID
�� <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'>
�� UUIDGenerator default generateBytes: self forVersion: 4.

On my machines/VMs/images the primitive works. Which means the UUIDGenerator is not needed, I can just as well throw it away. So it does not matter whether it is initialised correctly or not.

So the next question is: why does the primitive not work for some people ? Was it like that forever ? I don't think we want that kind of platform difference.

This really is misleading and confusion.

Sven