Comment 32 for bug 1685794

Note that "random: crng init done" appearing very late is not a problem by itself. User-noticeable delays only arise if some components (like Bluetooth?) require the crng init to be completed in order for themselves to initialize. This indicates poor design in those components (they should never block indefinitely waiting for /dev/random) and is not a problem with the random number generator itself.