[Solved] Slock crash after resume

Question

Hi there.
I recently experience something odd.
I call slock in /etc/systemd/system/[email protected] so that the screen is locked after resume.
What started only recently (I believe) is that (I assume) slock crashes about a minute after resume.
The only thing I can observe is that the lock screen is suddenly gone, without me touching anything.
If I enable slock manually this does not happen, so I assume that something kills slock.
Any ideas?
Last edited by PUE (2015-01-05 19:41:23)

Answer 1

$ cat /etc/systemd/system/[email protected]
[Unit]
Description=User suspend actions
Before=suspend.target
[Service]
User=%I
Type=forking
Environment=DISPLAY=:0
ExecStart=/usr/bin/slock
[Install]
WantedBy=suspend.target
There was no reference to slock in the journal. I will have to test again later. The journal output is obscured by:
...skipping...
No idea why anyone would think that it is helpful to not show part of the journal....
I have a couple of suspicious lines in there (reverse log because I don't know how to just search near the end), but I am not sure whether this is the problematic case:
Jan 04 14:29:54 eeyore systemd[1]: Stopped target Suspend.
Jan 04 14:29:54 eeyore systemd[1]: Stopping Suspend.
Jan 04 14:29:54 eeyore systemd[1]: Unit suspend.target is bound to inactive service. Stopping, too.
Jan 04 14:29:54 eeyore systemd-logind[295]: Operation finished.
Jan 04 14:29:54 eeyore systemd[1]: Reached target Suspend.
Jan 04 14:29:54 eeyore systemd[1]: Starting Suspend.
Jan 04 14:29:54 eeyore systemd[1]: [email protected] failed.
Jan 04 14:29:54 eeyore systemd[1]: Unit [email protected] entered failed state.
Jan 04 14:29:54 eeyore systemd[1]: Failed to start User suspend actions.
Jan 04 14:29:54 eeyore systemd[1]: [email protected] start operation timed out. Terminating.
Jan 04 14:28:44 eeyore systemd[469]: Time has been changed
Jan 04 14:28:44 eeyore systemd[1]: Time has been changed
Last edited by PUE (2015-01-05 17:54:01)