Another possibility is to split the gnutls random generator
initialization to preinitialization (open fds, check for getrandom()),
and initialization (read from the previous detected sources). That would
allow gnutls to be used on early boot without causing any delay. The
drawback would be some performance penalty on multi-threaded
environments on the usage of the random generator.
I have patch at: https://gitlab.com/gnutls/gnutls/merge_requests/111/
if you are interested for a review or comments.
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
NetworkManager takes very long to start, or times out, blocked on RNG
Status in Auto Package Testing:
Status in gnutls28 package in Ubuntu:
Status in network-manager package in Ubuntu:
Since a few days ago, NetworkManager.service takes awfully long to
start, or even times out on failure and then gets restarted. This
happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the
systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes
due to the NM timeout.
In the journal there is no actual logging from
/usr/sbin/NetworkManager yet, just the start timeout.
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.2-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
Date: Tue Sep 13 10:05:05 2016
# interfaces(5) file used by ifup(8) and ifdown(8)
iface lo inet loopback
UpgradeStatus: No upgrade log present (probably fresh install)
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.2.2 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~desktop-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp