Control: tag -1 +pending On Wed, 2016-07-13 at 08:31 +0200, Eduard Bloch wrote: > > Hi,
Hi, Thanks for you report, sorry for the delay getting back to you. > That's not really obvious! And it's also not clearly documented, i.e. I > cannot find a simple hint in README.Debian or in the manpage. The > manpage tells the story on how it's implemented but when user comes with > a different focus in mind (how to react to systemd, not some X11 events > or whatever) then it's not clear at all. TBH it never even occurred to me that this would be unclear, but I have tried to add some words to the man page noting that you need to run the tool in your xsession (see [0] below for the commit). I know basically nothing about systemd nor how it works wrt screensavers and therefore what is required there, although I do run xss-lock + systemd on my laptop and AFAICT it just works. If you want to propose some specific wording that you think would have been useful to you then I'd be happy to consider including them in a future upload. > Please change that. And please also consider adding into > /etc/X11/Xsession.d/ , maybe with some debconf switch. I'm afraid I think this would be going to far for the sort of tool xss- lock is so I don't intend to do this. Ian. commit 323b8eeb04a7e6a7b87ae7670c1eda6a3ca891ce Author: Ian Campbell <[email protected]> Date: Sun Aug 21 12:47:10 2016 +0100 Try to clarify usage via xsession or similar in xss-lock(1) (Closes: #830949) diff --git a/doc/xss-lock.1.rst.in b/doc/xss-lock.1.rst.in index 741b3df..e1b0840 100644 --- a/doc/xss-lock.1.rst.in +++ b/doc/xss-lock.1.rst.in @@ -20,8 +20,15 @@ Description =========== **xss-lock** hooks up your favorite locker to the MIT screen saver extension -for X and also to systemd's login manager. The locker is executed in response -to events from these two sources: +for X and also to systemd's login manager. + +**xss-lock** should be run in your xsession either by starting it in +your `.xsessionrc` or by other session specific means (e.g. Window +manager configuration). Note that **xss-lock** runs in the foreground +(i.e. doesn't fork) and therefore you may need to run it in the +background (for example by running with `&`). + +The locker is executed in response to events from these two sources: - X signals when screen saver activation is forced or after a period of user inactivity (as set with ``xset s TIMEOUT``). In the latter case, the notifier @@ -115,6 +122,11 @@ Notes Examples ======== +- Use with **xscreensaver** via `.xsessionrc` (hence in the background):: + + xscreensaver & + xss-lock -- xscreensaver-command --lock & + - Run **xlock** after ten minutes of inactivity:: xset s 600
