long delay at shutdown/reboot - network-manager doesn't close correctly

Status changed to 'Confirmed' because the bug affects multiple users.

I added a me to as well. It started last week for me, shut down times went from 3 seconds to more than 15 seconds on 4 different laptops.

same thing here too with QQ i386 : stop a few seconds at "remaining services" and have also some initctl unknown jobs (K20plymouth K20networking)

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1066484

This affects me too after an upgrade from 10.04. The last thing I see is after "nmdispatcher.action caught signal 15 shutting down ..." is :- "*All processes ended within 2 seconds" Then no activity for about 2 minutes and then it shuts down. There are messages just before is shuts down but are far too quick to read.

Here too, same problem and same messages... A fail in the shutting down due to the network manager and after several seconds it go down...

It seems to be solved for me. Shutdown is now as fast as it used to be.

Not here, always the same problem...
Nobody can fix it? :(

on RR i386, i was having that hang due to : modem-manager "caught signal 15, shutting down ..."

As wicd is now installed by myself (tired of n-m), i've purged network-manager & network-manager-gnome; and now ubuntu can close without hanging.

https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1024868

In fact I was wrong; from time to time it is OK (I'm not able to determine the cause though), but in general it keeps being very slow.

While trying to catch a samba related bug, Steve Langasek pointed me to this NM bug. The screenshot shows the "nm-dispatcher.action: Caught signal 15, shutting down..." message.

Steve's comment (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/comments/191):

Markus, your screenshot shows a network-manager error:

  nm-dispatcher.action: Caught signal 15, shutting down...

This indicates that some part of NM is not being correctly guarded from /etc/init.d/sendsigs, resulting in abnormal termination that breaks the network connection before network filesystems are being unmounted. Network Manager has previously been fixed for such bugs, but it seems to have recurred.

Mathieu, could you please look into this regression?

We are in 2014 and this bug still persists. I'm using Ubuntu Gnome Gnome 14:04 with 3.14.