Comment # 8 on bug 915160 from Marius Tomaschewski

Please ensure, that there is no wicked + NetworkManager running at same time.

They basically conflict with each other, e.g. both trying to reconfigure the
wpa-supplicant or both starting dhcp clients (wicked provides own one and is
not using dhclient at all) or reconfiguring the same interface.

See also bug#895447 (yast2 lan leaves part of NetworkManager running); more
exactly: switching between NetworkManager and wicked does not work properly.

The manual steps are to switch between are:

wicked-to-NM)

  ## stop wicked, any need to stop network
  systemctl stop wickedd.service

  ## disable all wicked services
  systemctl disable wicked.service

  ## enable NetworkManager (creates network.service link)
  systemctl enable NetworkManager.service

  ## start network / NetworkManager
  systemctl start network.service
;;

NM-to-wicked)

  ## stop NetworkManager and all helpers it started...
  systemctl --kill-who=all kill NetworkManager.service
  systemctl stop NetworkManager.service

  ## disable NetworkManager
  systemctl disable NetworkManager.service

  ## enable wicked services (creates network.service link)
  systemctl enable wicked.service

  ## start wickedd damones
  systemctl start wickedd.service

  ## start the network
  systemctl start network.service
;;