NmClient notifies active-connections property before emitting connection-added for wireguard vpn
When starting a wireguard vpn via wg-quick up vpnName
, the emission order of signals goes like this:
notify::active-connections
connection-added
This is causing bugs with gnome-shell's VPN indicator, because it adds and removes connections by listening to connection-added
and connection-removed
, and then expects a notify::active-connections
emission to happen after than in order to show the connection as active.
I'd assume the connection-added
signal should always be emitted first before anything else references a connection, just like the connection-removed
signal is supposed to be emitted last?