elogind and lock before suspend

Tonus · 12-30-2020, 04:22 PM

Hi all,

Running no power management tool with my WM and was looking for transition from pm-* commands to new elogind ones.

To lock before suspend, elogind uses scripts in /lib{,64}/elogind/system-sleep/

To auto-lock, a simple script like this should do the trick (single user board here, thank you for improvements if you know some)

Code:

username=<YOUR_USERNAME>
userhome=/home/$username
export XAUTHORITY="$userhome/.Xauthority"
export DISPLAY=":0"

            /usr/bin/xautolock -locknow &
            sleep 1s;

I will look for more universal way since telling the username varaiable isn't very reliable...

Bindestreck · 12-30-2020, 04:56 PM

Hey! This is mine:

Code:

#!/bin/bash

username=alexsson
userhome=/home/$username
export XAUTHORITY="$userhome/.Xauthority"
export DISPLAY=":0.0"
case "${1}" in
    pre)
        su $username -c "/usr/bin/i3lock -B 4 -k --timecolor=ffffff80 --datecolor=ffffff99" &
        sleep 1s;
        ;;
esac

Since, the script itself is executed by "root" (I believe, please correct me if I am wrong), one have to run the lock with a specified username. I would also like to know if it is possible to write a more general script where username is not required.

However, the script just works fine, no issues.

walecha · 12-30-2020, 07:15 PM

I think elogind should locks all running session prior to suspend/hibernate.

But if you want to do that by yourself, then using loginctl is preferred

Code:

loginctl lock-session $XDG_SESSION_ID

Tonus · 12-31-2020, 04:29 AM

Quote:

Originally Posted by walecha

I think elogind should locks all running session prior to suspend/hibernate.

Does it work for you ? It doesn't here. Neither your loginctl command does.

zhl · 12-31-2020, 04:48 AM

xss-lock will works correctly since the elogind replacement, see more https://wiki.archlinux.org/index.php..._lock#xss-lock, and the source code at https://bitbucket.org/raymonad/xss-lock. I prefer xss-lock, 'It will not be triggered when looking at videos.'

Bindestreck · 12-31-2020, 04:53 AM

On Fluxbox, none of the locks gets triggered when suspending. I had to add that script inside system-sleep (I am using i3lock btw).

walecha · 12-31-2020, 05:08 AM

Quote:

Originally Posted by Tonus

Does it work for you ? It doesn't here. Neither your loginctl command does.

You have to make sure that your login session is registered with elogind

This is my login session in my other slackware PC (via ssh):

Code:

[17:56:39] ~
 $ loginctl
SESSION  UID USER    SEAT  TTY
    c15    0 root    seat0 tty1
    c21 1000 walecha seat0 tty8  <- this my desktop session
    c24 1000 walecha       pts/2 <- this is my ssh login

3 sessions listed.

[18:05:40] ~
 $ loginctl unlock-session c21; sleep 3; loginctl show-session c21 | grep LockedHint
LockedHint=no


[18:06:01] ~
 $ loginctl lock-session c21; sleep 3; loginctl show-session c21 | grep LockedHint
LockedHint=yes

If I want to lock all login session then I just login as root and run:

Code:

# loginctl lock-sessions

Bindestreck · 12-31-2020, 05:13 AM

Do you know where I can find more information regarding elogind? I want to know how to change the "lock"-app, how to "register" e.t.c. The documentation seems to be difficult to find.

walecha · 12-31-2020, 06:49 AM

What is your i3 version?

I take a look in the SBo/desktop/i3lock for 14.2 and it is patched to disable pam support, see here.

In current which is using pam, to use elogind, the program must be linked to pam libraries.

IMHO, if you are using SBo 14.2 to build i3 for using in current, I think it's better to use the last available version of i3* so the SlackBuild needs some modification and don't disable pam support.

And maybe using xss-lock as locker:
Here is the snippet from i3 4.19 ${HOME}/.config/i3/config:

Code:

# xss-lock grabs a logind suspend inhibit lock and will use i3lock to lock the
# screen before suspend. Use loginctl lock-session to lock your screen.
exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock --nofork