Comment # 20 on bug 902771 from Marius Tomaschewski

(In reply to kevin vandeventer from comment #19)
> Wicked has started working for me with my wireless card but so far I have
> been unable to figure out exactly how it started working.
[...]
> I switched to IceWM to work around the plasma crashes and I switched to
                                                            ^^^^^^^^^^^^^
> wicked via command line and connected an ethernet cable to get a network
  ^^^^^^^^^^^^^^^^^^^^^^^
> connection.
[...]
> A recent email about bug #895447 said an update to sysconfig may help with
> this wicked problem, but mine starting working long before that.

The sysconfig update contains an update migration fix. It is required to stop
all processes of the NM service, because a "systemctl stop NetworkManager" is
not doing it (stops only the NetworkManager process, but not e.g. dhclient):

/usr/bin/systemctl --kill-who=all kill NetworkManager.service || :
/usr/bin/systemctl stop NetworkManager.service || :
/usr/bin/systemctl --force disable NetworkManager.service || :

The rest of this issue is about a correction of the wicked <-> NetworkManager
switch in yast2. Once fixed, using yast2 should be able to make it correctly.

> It's been working for about nine days. Now when I execute the status command,
> everything is 'up' and the only 'setup-in-progress' is because the ethernet
> isn't plugged in. 

When use-nanny is enabled, nanny will setup ethernet when there is a link.

We do not setup IP addresses on interfaces without a link, because a link
is required for:
  - bridge STP
  - authentication
  - lldp
  - duplicate address detection

There are some corner cases where it makes sense to ignore the link status
and just set up it (e.g. on a router) -- that is, we will add a config
switch allowing it. But this is an another issue:

> sudo systemctl  status network.service wickedd.service
> wpa_supplicant.service NetworkManager.service -l 
[...]
> wicked.service - wicked managed network interfaces
>   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
>   Active: active (exited) since Fri 2015-01-23 11:33:12 CST; 20min ago
[...]
> wickedd.service - wicked network management service daemon
>   Loaded: loaded (/usr/lib/systemd/system/wickedd.service; enabled)
>   Active: active (running) since Fri 2015-01-23 11:32:42 CST; 20min ago
> Main PID: 805 (wickedd)
>   CGroup: /system.slice/wickedd.service
>           ������805 /usr/sbin/wickedd --systemd --foreground
[...]

> NetworkManager.service - Network Manager                                    
>    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) 
>    Active: active (running) since Fri 2015-01-23 11:32:42 CST; 20min ago    
>  Main PID: 803 (NetworkManager)          
>    CGroup: /system.slice/NetworkManager.service 
>            ������ 803 /usr/sbin/NetworkManager --no-daemon
>            ������1608 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlp5s5.pid -lf /var/lib/NetworkManager/dhclient-89d89176-938b-4c00-b02c-0deb032a90ae-wlp5s5.lease -cf /var/lib/NetworkManager/dhclient-wlp5s5.conf wlp5s5

But as this output shows, your bug is a duplicate of bug #895447 -- you
still have both network services running ... again -> you stopped NM
(manually, see above) for a while and it started working but you did not
disabled the NetworkManager.service...
-> Please execute the 3 systemctl commands I've provided above as root.

Resolving as duplicate of bug#895447

*** This bug has been marked as a duplicate of bug 895447 ***