Comment # 3 on bug 1157394 from Knut Alejandro Anderssen Gonz�lez

(In reply to Russell Sandish from comment #0)
> Going into the network configuration panel, and selecting wicked as the
> network manager, and clicking edit on a wifi interface, it correctly scans
> and finds the SSIDs available. When selecting an SSID, the form indicates
> that the access point is "ad hoc" and unencrypted. I set the encryption to
> WPA2-PSK, and no matter whether I set the mode to ad hoc or managed, when I
> click next, yast2 immediately returns its starting panel (normally it would
> spend a while thinking while it configures the network), and networking is
> not configured.


The changes you have notice are mainly because we have done some
re-factorization in yast2-network module.

https://lizards.opensuse.org/2019/08/30/yast-sprint-83/

> 
> Wicked appears to be working correctly - I had saved some wicked
> configuration files, and I can load these and they work. But given wicked's
> XML configuration format doesn't appear to be documented, it has limited my
> ability to connect to new wifi connections that don't use the same
> encryption scheme.

YaST do not use wicked XML configuration directly, but still writes down the
ifcfg files which wicked reads for declaring it internal state. That is
something we have been discussing and maybe something yast-network will do in
the future. We have being modeling it in order to support multiple backends
like NM, wicked or even systemd-network but as said it is something we still do
not support. 

> 
> Normally, I do a zypper dup every week, so I always running close the the
> latest Tumbleweed distro.
> 
> I first noticed this problem on 30th October, when I upgraded my network
> equipment at home, and attempted to connect to the new Wifi 4 AP (aka
> 802.11ac). I can also confirm that it did work on October 15th, so the
> problem could not have arisen much before that date.


I already fixed a bug (https://bugzilla.suse.com/show_bug.cgi?id=1155639)
related to WPA2-PSK configuration that will be available in
yast2-network-4.2.26, so it could be already fixed.

See https://github.com/yast/yast-network/pull/1001

But would be nice to have some feedback, so, once you get the new version,
could you verify if you are still experimenting some problem related to
WPA2-PSK configuration?