From dfb7cb555e3c244d49a1243e950d24f83d4cc20b Mon Sep 17 00:00:00 2001
From: Vincent Bernat <vincent@bernat.ch>
Date: Thu, 15 Jul 2021 11:35:19 +0200
Subject: [PATCH] xss-lock: do not trigger a XRandR event

I need to fix that later...
---
 bin/xss-lock | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/bin/xss-lock b/bin/xss-lock
index 8c63547..61c8340 100755
--- a/bin/xss-lock
+++ b/bin/xss-lock
@@ -25,10 +25,10 @@ case "$1" in
         trap "systemctl --user kill -s CONT redshift@${display}.service" EXIT
         trap 'echo notify: user activity; kill %% 2> /dev/null; exit 0' HUP  # user activity
         trap 'echo notify: locker started; kill %% 2> /dev/null; exit 0' TERM # locker started
-        outputs=($(xrandr --current | sed -n 's/\([^ ]*\) connected .*/\1/p'))
-        for out in ${outputs[@]}; do
-            xrandr --output $out --brightness 0.2
-        done
+        # outputs=($(xrandr --current | sed -n 's/\([^ ]*\) connected .*/\1/p'))
+        # for out in ${outputs[@]}; do
+        #     xrandr --output $out --brightness 0.2
+        # done
         sleep infinity &
         wait
         echo "notify: end"