http://bugzilla.suse.com/show_bug.cgi?id=893678 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #30 from Marius Tomaschewski <mt@suse.com> --- Your logs show, that NetworkManager is still running. Use: systemctl --kill-who=all kill NetworkManager.service systemctl stop NetworkManager.service systemctl disable NetworkManager.service systemctl --force enable wicked.service systemctl --force enable wpa_supplicant.service systemctl daemon-reload then either: systemctl restart wpa_supplicant.service systemctl restart wickedd.service systemctl restart wicked.service or: reboot finally, provide the output of (redirect to file to attach it later): systemctl status network.service wickedd.service wpa_supplicant.service NetworkManager.service ps axwww | grep -E "dhc|NetworkManager" | grep -v grep the results should be: wicked.service (network.service), wickedd.service, wpa_supplicant.service -> loaded/enabled and active and NetworkManager.service -> loaded/_disabled_ and _inactive and there is no dhcp client other than wickedd-dhcp* running. (In reply to kevin vandeventer from comment #28)
If there is a conflict between NetworkManager and wicked it must be there without me even starting NM for the first time after a fresh install.
_yes_ yast2-network is unable to switch properly between NetworkManager and wicked and stop NetworkManager properly/completely. When NetworkManager and wicked* are running at the same time, both are trying to (re)configure wpa_supplicant and both are statring dhcp clients and (re)configuring the same interfaces. That is, as long as they run at the same time, it will not work and it is simply a duplicate of the another bug -> I'm resolving as such now. When you boot and wicked is unable to set up an interface _and_ there are no conflicting engines such as NetworkManager running -> please open a new bug report and provide logs as requested. *** This bug has been marked as a duplicate of bug 895447 *** -- You are receiving this mail because: You are on the CC list for the bug.