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 19:53:40 legend systemd-sleep[11810]: xtrlock (version 2.5): > cannot open display This is what happens if XOpenDisplay(0) returns NULL, which means that the program could not connect to the display specified in $DISPLAY. I think it is very unlikely that this is a bug in xtrlock. > When I run the file as root, e.g. `sudo /lib/systemd/system-sleep/lock-screen` > the screen is locked as expected. For some reason, display :0 is not > available when the system is suspended. As noted earlier, this way of > locking the screen was working before the upgrade. I suspect, therefore, that systemd is at fault? Regards, Matthew -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
