Blame SOURCES/wake-up-on-deactivate.patch

f31430
From d6ead50fe230df58ddab822966d69760b00ec920 Mon Sep 17 00:00:00 2001
f31430
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
f31430
Date: Wed, 1 Apr 2020 14:48:10 +0200
f31430
Subject: [PATCH 1/2] screenShield: Switch lightboxes off before unlock
f31430
 transition
f31430
f31430
There is no point in animating a transition with fullscreen black
f31430
rectangles stacked on top, so switch them off before rather than
f31430
after the transition.
f31430
f31430
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1158
f31430
---
f31430
 js/ui/screenShield.js | 5 +++--
f31430
 1 file changed, 3 insertions(+), 2 deletions(-)
f31430
f31430
diff --git a/js/ui/screenShield.js b/js/ui/screenShield.js
f31430
index cd38f11fc8..282f29fa30 100644
f31430
--- a/js/ui/screenShield.js
f31430
+++ b/js/ui/screenShield.js
f31430
@@ -1221,6 +1221,9 @@ var ScreenShield = class {
f31430
             this._isModal = false;
f31430
         }
f31430
 
f31430
+        this._longLightbox.hide();
f31430
+        this._shortLightbox.hide();
f31430
+
f31430
         Tweener.addTween(this._lockDialogGroup, {
f31430
             scale_x: 0,
f31430
             scale_y: 0,
f31430
@@ -1237,8 +1240,6 @@ var ScreenShield = class {
f31430
             this._dialog = null;
f31430
         }
f31430
 
f31430
-        this._longLightbox.hide();
f31430
-        this._shortLightbox.hide();
f31430
         this.actor.hide();
f31430
 
f31430
         if (this._becameActiveId != 0) {
f31430
-- 
f31430
2.28.0
f31430
f31430
f31430
From 39ac7cad68d8c00d98c900b35add637b01eddbbf Mon Sep 17 00:00:00 2001
f31430
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
f31430
Date: Tue, 31 Mar 2020 21:07:59 +0200
f31430
Subject: [PATCH 2/2] screenShield: Wake up on deactivate()
f31430
f31430
Usually the screen is woken up before the shield is deactivated, but
f31430
it is also possible to unlock the session programmatically via the
f31430
org.gnome.ScreenSaver D-Bus API.
f31430
f31430
The intention is very likely not to unlock a turned off screen in
f31430
that case. Nor does it seem like a good idea to change the lock
f31430
state without any indication.
f31430
f31430
Waking up the screen is more likely to meet expectations and is
f31430
more reasonable too, so do that.
f31430
f31430
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1158
f31430
---
f31430
 js/ui/screenShield.js | 2 ++
f31430
 1 file changed, 2 insertions(+)
f31430
f31430
diff --git a/js/ui/screenShield.js b/js/ui/screenShield.js
f31430
index 282f29fa30..2d0a429bee 100644
f31430
--- a/js/ui/screenShield.js
f31430
+++ b/js/ui/screenShield.js
f31430
@@ -1200,6 +1200,8 @@ var ScreenShield = class {
f31430
         if (Main.sessionMode.currentMode == 'unlock-dialog')
f31430
             Main.sessionMode.popMode('unlock-dialog');
f31430
 
f31430
+        this.emit('wake-up-screen');
f31430
+
f31430
         if (this._isGreeter) {
f31430
             // We don't want to "deactivate" any more than
f31430
             // this. In particular, we don't want to drop
f31430
-- 
f31430
2.28.0
f31430