Bug#789413: xtrlock: "Cannot open display" when called from /lib/systemd/system-sleep

2019-07-21 Thread Chris Lamb
Hi, > > xtrlock: "Cannot open display" when called from /lib/systemd/system-sleep It is likely that the DISPLAY variable is being masked from the final xtrlock binary. $ DISPLAY=":0.0" su myusername -c "xtrlock" & Can you try: $ su myusername -c "env DISPLAY=:0.0 xtrlock" & … or similar?

Bug#789413: xtrlock: "Cannot open display" when called from /lib/systemd/system-sleep

2015-06-23 Thread Matthew Vernon
tags 789413 moreinfo quit Hi, > I have the following contents in the file /lib/systemd/system-sleep > The file is owned by root and executable. > DISPLAY=":0.0" su myusername -c "xtrlock" & Are you sure DISPLAY is set appropriately, and/or being passed through to xtrlock? > Jun 19

Bug#789413: xtrlock: "Cannot open display" when called from /lib/systemd/system-sleep

2015-06-20 Thread JJ Vens
Package: xtrlock Version: 2.7 Severity: normal Dear Maintainer, I have the following contents in the file /lib/systemd/system-sleep The file is owned by root and executable. #!/bin/bash if [ "$1 $2" == "pre suspend" ] then DISPLAY=":0.0" su myusername -c "xtrlock" &