I get some of those in my .xsession-errors file:
localuser:paul being added to access control list
dbus: Failed to start message bus: Failed to generate UUID: Could not open /dev/urandom: No such file or directory
EOF in dbus-launch reading address from bus daemon
dbus-update-activation-environment: not on Linux, ignoring --systemd argument
dbus-update-activation-environment: error: unable to connect to D-Bus: /usr/bin/dbus-launch terminated abnormally with the following error: EOF in dbus-launch reading address from bus daemon
This seems to result in Xorg trying to abort, but not having the rights to do so... sorry I will try recopy exact message when I see it... if useful.
I also remember that during installation, I think package zlib1g, complains about /dev/random file not existing...
wait: now reading:
paul@debian:~$ cat /hurd/random-hurd.sh
exec /hurd/random --seed-file /var/lib/random-seed
I now think the error message in the installer was that /var/lib/random-seed did not exist.
So we have /dev/random... but not /dev/urandom
Searching "urandom vs random" I get:
Résultats de recherche d'images pour « urandom vs random »
'Urandom' is used where there is constant need of random numbers and its randomness is not much important while 'random' is used where there is a security concern and its randomness should be reliable as it blocks outputting random numbers if entropy is not up to the mark."
So it looks like /dev/urandom should be easier to get than /dev/random... maybe I could "settrans -cp /dev/urandom /hurd/random"?