Closed nenad closed 5 years ago
i3lock uses XCB, which uses libXau, which pretty much every piece of software uses for X authentication, so there shouldn’t be a difference here.
My guess is that lxdm sets the XAUTHORITY
environment variable, resulting in programs picking up the correct location without needing the symlink. In your service file, try setting not only DISPLAY
, but also XAUTHORITY
.
Thanks for the answer! I can't test it since I've moved to using sway, but I'm pretty confident your solution will work.
I know its been a while since this issue was closed, and dont know if you would read this, but I wanted to thank you a lot, I was having the same issue and this helped me..
Since I moved to using
lxdm
I noticed my systemctl service for locking on suspend started failing with the following message:This is how the script looks like:
The
betterlockscreen
is a very simple image manipulator which uses i3lock (https://github.com/pavanjadhaw/betterlockscreen/)LXDM puts the
.Xauthority
file in/run/lxdm/$UID/.Xauthority
. I symlinked it from there to~/.Xauthority
and it works now, but I'm not sure if this can be fixed in i3lock itself.