From dd042ae5948b64c113d4a0f8a1bc8bbf9c33badc Mon Sep 17 00:00:00 2001
From: Vincent Bernat <vincent@bernat.ch>
Date: Mon, 21 Jun 2021 22:10:54 +0200
Subject: [PATCH] xss-lock: don't suspend compositor on lock

Let's see if the confidentiality issue is still here. The problem with
suspending the compositor is that Firefox with EGL will freeze its
rendering. See https://bugzilla.mozilla.org/show_bug.cgi?id=1712665.

OK, the problem was that when screens are added/removed, i3lock is
unable to stay on top. I'll live with that for now.
---
 bin/xss-lock | 2 --
 1 file changed, 2 deletions(-)

diff --git a/bin/xss-lock b/bin/xss-lock
index 53dc631..a924f19 100755
--- a/bin/xss-lock
+++ b/bin/xss-lock
@@ -40,9 +40,7 @@ case "$1" in
         # First, pause any music player
         playerctl -a pause
         # Then, lock screen
-        systemctl --user stop compton@${display}.service
         i3lock -n -e -i $HOME/.cache/awesome/current-wallpaper-${display}.png -t -f
-        systemctl --user start compton@${display}.service
         echo "lock: unlock screen"
         ;;
 esac