Florian Müllner d3a3b7f514 screenShield: Do not save lock state on wayland ... We keep track of the lock state and restore it on startup to prevent a crash from bypassing the screen lock. However on wayland, a crash doesn't result in gnome-session restarting gnome-shell, but brings down the entire session - that is, restoring the lock state does not actually protect the existing session in that case, but forces the user to authenticate twice in order to start the next session. This is clearly not helpful, so avoid this by not saving the state when running as wayland compositor. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/17		2018-02-07 04:35:57 +00:00
..
extensionPrefs	Define classes with 'var' instead of 'const'	2017-07-18 21:52:06 +02:00
gdm	gdmUtils: Define constants with 'var'	2017-08-10 20:16:06 +02:00
misc	misc: Make IBus a mandatory dependency	2018-02-05 17:46:57 +01:00
perf	Revert accidental commit "Test stuff"	2014-09-03 13:47:18 -04:00
portalHelper	Define classes with 'var' instead of 'const'	2017-07-18 21:52:06 +02:00
ui	screenShield: Do not save lock state on wayland	2018-02-07 04:35:57 +00:00
js-resources.gresource.xml	thunderbolt: add policy provider and indicator	2018-02-05 21:38:49 +01:00
meson.build	build: Support the meson build system	2017-07-20 00:20:54 +02:00