Jonas Dreßler 723c0a6e61 status/network: Sync active connections again on connection-added ... NetworkManagers NmClient has a bug for wireguard connections where the notify::active-connections and connection-added are emitted in the wrong order: When a wireguard connection gets activated, notify::active-connections is emitted first, then connection-added happens. We currently expect these signals to emitted in the correct order, so our VPN toggle is not actually updated when a wireguard connection is established. Until this bug is fixed in NetworkManager, work it around by calling _syncActiveConnections() manually after we see ::connection-added. NM issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1483 Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6656 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3219>		2024-03-01 17:32:07 +01:00
..
dbusServices	dbusServices/extensions: Override destroy() method	2024-03-01 15:00:46 +00:00
extensions	extensions: Fix ngettext convenience	2023-09-15 21:41:30 +00:00
gdm	loginDialog: Close conflicting session dialog after 60 secs	2024-02-29 20:42:52 +00:00
misc	loginManager: Add session-removed signal and getSession method	2024-02-29 20:42:52 +00:00
portalHelper	js: Port Config to ESM	2023-08-10 17:42:23 +00:00
ui	status/network: Sync active connections again on connection-added	2024-03-01 17:32:07 +01:00
js-resources.gresource.xml	dbusErrors: Add utility module for handling remote errors	2024-01-31 20:58:31 +01:00
meson.build	extensions-app: Move Extensions app to new subproject	2020-03-27 23:33:30 +00:00
portal-resources.gresource.xml	js/portal-resources: Add missing fileUtils to js path	2022-11-03 18:02:27 +00:00