From 3ed379c25da686bc7b576ec8621cad6f1a098651 Mon Sep 17 00:00:00 2001
From: Maximilian Friedersdorff <max@friedersdorff.com>
Date: Wed, 17 Oct 2018 11:13:59 +0100
Subject: [PATCH] Launch light-locker from i3 config

light-locker must be started after the dbus-session
is already running.  This can be guaranteed when i3 is
running
---
 X/.xprofile               | 5 -----
 i3/.config/i3/config.base | 4 +++-
 2 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/X/.xprofile b/X/.xprofile
index 59defe4..f131b88 100644
--- a/X/.xprofile
+++ b/X/.xprofile
@@ -51,11 +51,6 @@ esac
 
 cat ~/.ratpoisonrc.base ~/.ratpoisonrc.$HOSTNAME > ~/.ratpoisonrc
 
-# run xcreensaver
-if [ -x $(which xscreensaver) ]; then
-  xscreensaver&
-fi
-
 # configure i3
 
 if [ -f ~/.config/i3/config.base ]; then
diff --git a/i3/.config/i3/config.base b/i3/.config/i3/config.base
index e4795ab..22fbce8 100644
--- a/i3/.config/i3/config.base
+++ b/i3/.config/i3/config.base
@@ -104,7 +104,7 @@ mode "$ratpoison" {
 
     bindsym Escape mode "default"
 
-    bindsym $mod+l mode "default" exec "i3lock -i ~/Pictures/lockscreen.png"
+    bindsym $mod+l mode "default" exec "light-locker-command -l"
 
 }
 
@@ -178,3 +178,5 @@ focus_follows_mouse no
 focus_on_window_activation urgent
 
 for_window [class="^rdesktop"] move workspace number 9; floating disable
+
+exec light-locker&
-- 
2.45.2