Hi Max, Using 64-bit 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 2013 from the 2013-04_02 daily build:
1. NetworkManager stopped correctly (immediately) via sudo stop network-manager. 2. A reboot to an alternate system and fsck of the system under test presented errors. Regardless of whether I stopped or restarted NetworkManager, as long as I manually unchecked Enable Networking, a clean shutdown would occur and a subsequent fsck would show no errors. A process (maybe more than one) is being gracefully shut down when I manually uncheck Enable Networking but is not getting properly shutdown via sudo stop network-manager. Hope this data point is helpful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1124803 Title: NetworkManager doesn't respond to SIGTERM in daemon mode Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” package in Gentoo Linux: New Bug description: NetworkManager does not respond to SIGTERM when started in daemon mode, as upstart does by default. This also happens when running NetworkManager manually from the command line as long as the --no- daemon option is not used. This was reported upstream and was fixed by commit 64342a313ef497fca8a4fb7567900d4a1460065f It appears that this bug forces upstart to SIGKILL NetworkManager during shutdown, which, amoung other things, means that n-m doesn't deconfigure network interfaces as intended. This bug, along with bug 1124789 (in wpasupplicant), means that no attempt is made to disconnect from a wifi network during shutdown. This in turn triggers a bug in my BIOS which causes this system to hardlock in the middle of BIOS post when I reboot while still connected to a wifi network: http://thread.gmane.org/gmane.linux.kernel.wireless.general/102862 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4 Uname: Linux 3.5.0-24-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Wed Feb 13 22:32:52 2013 IpRoute: default via 10.179.201.1 dev eth0 proto static 10.179.201.0/24 dev eth0 proto kernel scope link src 10.179.201.80 metric 1 10.179.201.0/24 dev wlan0 proto kernel scope link src 10.179.201.105 metric 9 169.254.0.0/16 dev eth0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2012-10-20 (116 days ago) WpaSupplicantLog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-03-21T22:57:56 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0 connected enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1124803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
