@adamwill it is probably related to the changes how NetworkManager configures systemd-resolved. Is it possible to add some printf debugging statements before the failure? In particular
resolvectl ; nmcli device ; ip addr ; ip route.
Btw, yesterday we also released 1.28.0 which is now in rawhide (package "1.28.0-1"). That might have exactly the same problem. Does it?
Thank you for having extensive CI tests! That is awesome!!
NetworkManager doesn't launch wpa_supplicant. The supplicant is started via D-Bus activation. Whether that includes -Dwext or not, is not related to NetworkManager. Please open a bug against supplicant, if you want to change that. On fedora, that is configured via /etc/sysconfig/wpa_supplicant
@dimitrisk, I don't have any say in that, but I would hope to not get it, because it still breaks all users of openvpn and use the deprecated
--tls-remote option in their ovpn files (not NetworkManager users). I don't think such a change is f25 material.
2.4 removes the --tls-remote option, which breaks existing configurations for users on F24. Even worse, NetworkManager-openvpn plugin on Fedora 24 does not support the --verify-x509-name. I voting -1 for pushing such an update to old-stable f24 release.