FS#31115 - [NetworkManager] 0.9.6.0-1 brings back bug #30305
Attached to Project:
Arch Linux
Opened by Ryan (Kirby) - Sunday, 12 August 2012, 21:19 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 19 September 2012, 08:16 GMT
Opened by Ryan (Kirby) - Sunday, 12 August 2012, 21:19 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 19 September 2012, 08:16 GMT
|
Details
Description:
After enable the testing repositories and updating networkmanager to 0.9.6.0-1, SIGTERM hangs for a few seconds, then displays FAILS and moves on. Exact same problem as this https://bugs.archlinux.org/task/30305 I never had such a problem with networkmanager 0.9.4.0-6, either Additional info: networkmanager 0.9.6.0-1 can remedy the problem by removing networkmanager from rc.conf, but of course, I lose the functionality. Steps to reproduce: Shutdown/Restart from KDE start menu |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Wednesday, 19 September 2012, 08:16 GMT
Reason for closing: Fixed
Additional comments about closing: 0.9.6.0-2
Wednesday, 19 September 2012, 08:16 GMT
Reason for closing: Fixed
Additional comments about closing: 0.9.6.0-2
I don't seem to notice any noteworthy errors at startup or shutdown. I uploaded the log of NetworkManager starting up, just in case I missed something.
I also noticed that networkmanager can't be SIGTERMed when daemonized, only SIGKILLed. If I don't run it as a daemon, SIGTERM takes care of it fine at shutdown
doesn't look like this changed anything, except for some extra dhclient lines
I have the pptp and openvpn plugins installed, but no VPN set up. I had the problem before installing those plugins
In addition I can provide this information: when NetworkManager started as daemon it does not respond to the SIGTERM signal (therefore it does not shut down while rebooting/shutting down the system), but when I launched it with --no-daemon command line parameter it exited on SIGTERM.
I'm sorry for my English. :-)