Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#44895 - [networkmanmager] nfs & systemd: a stop job is running...

Attached to Project: Arch Linux
Opened by Stefan Förster (HotblackDesiato) - Thursday, 07 May 2015, 22:15 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 09 May 2015, 15:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No



I have a desktop and two notebooks that use networkmanager to connect to my LAN via WiFi. I have an NFS server and all three machines connect to an NFS share during bootup. At shutdown, I regularly receive a "A stop job is running..." message from systemd on all three machines, since the network connection is already cvlosed and the NFS share unmounted, but systemd still tries to stop the networkmanager.service properly.

Even worse, since the last update of systemd, the stop job message never stops, it counts until 1min30s and then counts until 3mins and then untils ...

In a forum post I have found a solution that works. According to this post, the patch in the networkmanager.service files should already be upstream. Unfortunately, in the recent update from 1.0.1 to 1.0.2, this patch is not in the Arch Linux package.

The following changes need to be made:


When using wpa_supplicant, a similar change needs to be done to its service file:
This task depends upon

Comment by Stefan Förster (HotblackDesiato) - Sunday, 28 June 2015, 09:57 GMT
I just updated to systemd version 221. The two target files are still not patched. I can repro the bug under version 221, too. I have patched the files manually again.