http://bugzilla.suse.com/show_bug.cgi?id=895447 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@suse.com --- Comment #10 from Marius Tomaschewski <mt@suse.com> --- The only possibility to workaround it in yast2-network I currently see, would be to implement the "switch away from NM" like this -- and also to document in the release notes (for users doing it manually): # bnc#895447: NetworkManager does not cleanup on stop # Ensure it is gone along with conflicting dhclients, # ... before we switch over to another network.service. systemctl --kill-who=all kill NetworkManager.service systemctl stop NetworkManager.service systemctl disable NetworkManager.service Is this the way preferred by the NetworkManager? -- You are receiving this mail because: You are on the CC list for the bug.