If a WPA2-enterprise (i.e. non-PSK for the purposes of this issue) network is defined in wpa_supplicant.conf, and the user interacts with the lxplug-network icon (just opening and closing the GUI is enough) then the line disabled=1 will be added to the stanza describing the network in wpa_supplicant.conf.
This effectively allows desktop users to break networks that were correctly configured by hand, but then not fix them. I would propose not modifying networks that cannot be configured using the UI.
I observed this behavior with lxplug-network and the maintainer suggested that I report it upstream: https://github.com/raspberrypi-ui/lxplug-network/issues/7
If a WPA2-enterprise (i.e. non-PSK for the purposes of this issue) network is defined in wpa_supplicant.conf, and the user interacts with the lxplug-network icon (just opening and closing the GUI is enough) then the line
disabled=1
will be added to the stanza describing the network in wpa_supplicant.conf.This effectively allows desktop users to break networks that were correctly configured by hand, but then not fix them. I would propose not modifying networks that cannot be configured using the UI.