- 
    Bug 
- 
    Resolution: Done
- 
    P1: Critical 
- 
    5.10.0 Alpha
- 
    None
Boot time of B2Qt is really long with Qt 5.10. This is because QRandomGenerator now uses getentropy which blocks during boot until kernel outputs message "random: nonblocking pool is initialized".
At least qdbd and qtlauncher are affected by this.
Possible solutions:
- Disable feature "getentropy" from Boot2Qt builds
	- This is the behavior in Qt < 5.10.x
- Only difference in the entropy of randomness is in early boot
 
- Add "rng-tools" for inputting entropy to the kernel
	- Speeds up initialization of nonblocking pool
- On devices with HW random generator, this adds real entropy to the kernel pool
- On devices without HW random generator, this adds entropy from /dev/urandom to the kernel pool
 
- SettingĀ  QT_HASH_SEED for the affected processes
	- export QT_HASH_SEED=0
- export QT_HASH_SEED=`dd if=/dev/urandom bs=1 count=4 2>/dev/null | hexdump -v -e '1/1 "%u"'`
 
- Something else...
Some discussion about the issue is in comments of QTBUG-63029
- relates to
- 
                    QTBUG-63029 The qdbd connection to Apalis iMX6 broken on 5.10 -         
- Closed
 
-         
| For Gerrit Dashboard: QTBUG-63188 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V | 
| 205817,2 | Fix /dev/hwrng on Warp7 devices | pyro | yocto/meta-boot2qt | Status: MERGED | +2 | 0 | 
| 205840,2 | rng-tools: include RNG daemon to image | pyro | yocto/meta-boot2qt | Status: MERGED | +2 | 0 |