Dear Maintainer,
The bug still persists on fresh stretch and buster installations.
Is there any chance this could get fixed, or could you close this bug
with a wontfix and give a reason on why it's not? Seeing that the bug
persists for 3 years now.
Thank you.
Information for other people running into this problem:
For a configuration in /etc/network/interfaces:
allow-hotplug eth0
iface eth0 inet dhcp
The boot process is blocked with this message:
configuring network interfaces... ifup: waiting for lock on
/run/network/ifstate.eth0
One workaround seems to be to change allow-hotplug to auto, however,
this makes the boot process block when no cable is plugged in, just
before the tty login, because dhclient tries to get a DHCP answer and
waits for several attempts to timeout.
This might be irrelevant when you have an auto-starting graphical
desktop environment, because that just hides the dhcp messages and you
don't need a tty login on tty1.
Another workaround might be to use network-manager. Not tried so far, as
it conflicts with other packages on my setup.
Related forum thread (in spanish):
https://exdebian.org/foro/ifupwaiting-lock-runnetworkifstateeth0
