I was worried that my computer could be compromised and my login session is being hijacked by some malicious hook.
In .xsession executed by xdm, I capture a pstree snapshot a file to debug this situation.
This file's timestamp shows five to fifteen second delay after X11 login!
.xsession-errors doesn't show anything weird, only that I'm being added to "access control list" and then a couple of environment entries reported by dbus-update-activation-environment with no timestamps.
dmesg during this weird pause:
r8168: eth0: link up
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
random: crng init done
random: 7 urandom warning(s) missed due to ratelimiting
audit: type=1400 audit(1546022714.845:26): apparmor="STATUS" [...]
bridge: filtering via arp/ip/ip6tables is no longer available [...]
Bridge firewalling registered
Initializing XFRM netlink socket
IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): br-f14696ee8bfd: link is not ready
Regardless of the root cause (I suspect something demands more randomness after boot), how such problems can be debugged further?
Can I leverage systemd for example?