[SOLVED] xss-lock does not die on logout

bnb2235 · 2014-09-25 00:56:51

Hello,
I am trying to find a workaround for the problem I mentioned here
So far I have installed i3lock from the standard repository and xss-lock from the AUR. I disabled screen locking and screen blanking in Gnome. I added the following desktop files to both users ~/.config/autostart

[Desktop Entry]
Type=Application
Exec=xss-lock -- 'xautolock -locknow'
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_US]=SuspendLock
Name=SuspendLock
Comment[en_US]=AutoLock the screen before suspend
Comment=AutoLock the screen before suspend

[Desktop Entry]
Type=Application
Exec=xautolock -time 3 -locker 'i3lock -d -c 000000'
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_US]=XautoLock
Name=XautoLock
Comment[en_US]=AutoLock the screen
Comment=AutoLock the screen

I also added a custom keyboard shortcut:
xautolock -locknow
with the accelerator set to Super+L

So far, it seems like this will work fine. It seems to be working better than GDM locking. I have seen one problem thus far... If I log out of Gnome, xss-lock continues to run. If I log in again, I get a new xss-lock process. The original process continues to run and has one core at 100% load. If I log out again and log in again, I get yet another xss-lock process. This also runs at 100% load. This same phenomenon happens if I start the xss-lock from a terminal. xss-lock does not die on logout...

Why does xss-lock not die on logout?

Should I be using a systemd service file instead of xss-lock? I did try the service file, but it seems to work inconsistently because the DISPLAY variable continues to change.

Any suggestions?

Last edited by bnb2235 (2014-09-28 12:17:32)

halocaridina · 2014-09-25 01:41:05

Hi bnb2235,

I've seen the same behavior from xss-lock. This is what I've done to set things up with i3 on my laptop:

1) I don't use systemd and/or an autostart file for xss-lock

2) I start xss-lock with the following line near the end of my i3 config file:

exec --no-startup-id xss-lock -- i3lock -b -i /home/username/.config/i3/metal_grid_w_arch.png &

3) My i3 nagbar looks like so in the i3 config file:

 # exit i3 (logs you out of your X session)
bindsym $mod+Shift+e exec --no-startup-id "/usr/bin/paplay /usr/share/sounds/Feather/beep.wav && i3-nagbar -f pango:Arimo -t warning -m 'WHAT DO YOU WANT TO DO?:' -b 'Shutdown?' 'systemctl poweroff' -b 'Reboot?' 'systemctl reboot' -b 'Exit i3?' 'killall xss-lock && killall nm-applet && i3-msg exit'"

So I explicitly kill xss-lock and nm-applet priot to i3 being exited. This has kept xss-lock from exhibiting the behavior you describe (as well as prevents coredumps from nm-applet when i3 exits).

Last edited by halocaridina (2014-09-25 01:43:52)

mar04 · 2014-09-25 04:43:00

It has been fixed in git about 6 months ago, try xss-lock-git from AUR.

halocaridina · 2014-09-25 15:30:14

mar04,

Thanks for the suggestion of xss-lock-git. If I remember correctly, the bug was identified, but not fixed, at the time I installed xss-lock. Hence my workaround.

Since both package are available only from AUR, best to install xss-lock-git (which I just did after uninstalling xss-lock, and the git version behaves as expected upon exit).

bnb2235 · 2014-09-25 23:46:39

Thanks to both of you...
xss-lock-git does seem to fix the problem. I will mark this as solved.

I am curious why I did not find this issue when I googled the symptoms. Even now, I only find this thread. I guess I don't know the right keywords...?

halocaridina · 2014-09-26 03:01:50

Hi bnb2235,

Glad it worked out in the end. Regarding your Google searches on the problem:

I don't think xss-lock is that well known and/or utilized, thus the low return on searches. I finally discovered it after following many forum threads on screen-locking after a certain time interval. Given that many Linux distros (i.e., [U,K,X]buntu, Fedora, etc) come with a full DE out-of-the-box that includes this functionality as part of a screensaver or power management results in a smaller user base in general.

Cheers and have fun.

Arch Linux

#1 2014-09-25 00:56:51

[SOLVED] xss-lock does not die on logout

#2 2014-09-25 01:41:05

Re: [SOLVED] xss-lock does not die on logout

#3 2014-09-25 04:43:00

Re: [SOLVED] xss-lock does not die on logout

#4 2014-09-25 15:30:14

Re: [SOLVED] xss-lock does not die on logout

#5 2014-09-25 23:46:39

Re: [SOLVED] xss-lock does not die on logout

#6 2014-09-26 03:01:50

Re: [SOLVED] xss-lock does not die on logout

Board footer