Jonas Dreßler 1e68e78d8e extensionPrefs: Block notify::active signal handler while updating state ... We disable and enable extensions inside the `notify::active` signal handler, but we shouldn't do that in case the change didn't come from the user but because something else changed the state of the extension. This causes an issue when the extensionPrefs window is open and the session gets locked: The extensions are temporarily disabled by the shell, extensionPrefs updates its switches on the state change and adds those extensions to the `disabled-extensions` gsettings key inside the signal handler. Now when the session is unlocked again, the extensions won't be enabled again since they're forced-disabled. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/705		2019-09-09 19:50:31 +00:00
..
extensionPrefs	extensionPrefs: Block notify::active signal handler while updating state	2019-09-09 19:50:31 +00:00
gdm	realmd: Set login format to null on start and update if invalid	2019-09-09 19:28:18 +00:00
misc	windowManager: Handle starting/stopping of X11 services	2019-09-05 07:42:46 +00:00
perf	perf: Shut up another eslint error	2019-07-24 00:28:45 +02:00
portalHelper	cleanup: Mark globals used from other modules as exported	2019-07-24 00:28:45 +02:00
ui	iconGrid: Queue a relayout after child opacity changes	2019-09-09 19:39:28 +00:00
js-resources.gresource.xml	accessibility: Add pointer accessibility support	2019-06-06 09:13:29 +02:00
meson.build	build: Use dedicated resources for helper programs	2018-08-14 17:28:04 +00:00
portal-resources.gresource.xml	build: Include params.js in portal-helper gresources	2018-10-23 15:38:31 +00:00
prefs-resources.gresource.xml	build: Use dedicated resources for helper programs	2018-08-14 17:28:04 +00:00