Comment 20 for bug 1706939

Revision history for this message
AB (ablegox) wrote : Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

this is an annoying issue, i had the same on a fresh installation of arfull on my dell inspiron 5570.

i think we have two separate issues:

A) [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit)

systemd-networkd-wait-online.service fails to start and it adds +2min delay at startup when your wired Ethernet is not connected.

looking at that https://github.com/systemd/systemd/issues/2154

I start the service by adding --ignore=enp2s0 in /lib/systemd/system/systemd-networkd-wait-online.service

[Service]
Type=oneshot
ExecStart=/lib/systemd/systemd-networkd-wait-online --ignore=enp2s0
RemainAfterExit=yes

Now i have:

time sudo /lib/systemd/systemd-networkd-wait-online --ignore=enp2s0
ignoring: enp2s0
ignoring: lo

real 0m0.023s
user 0m0.006s
sys 0m0.013s

B) a stop job ... or kworker blocked... msg at Shutdown, reboot ..
looking at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724317

I've fixed upgrading the kernel to 4.13.10.