You are not logged in.
I am trying to get xss-lock with xsecurelock to autostart. It seems like it does, but
xset s activate
will make the screen flash black, and not much else.
Also i cannot find xss-lock together with all other running processes.
When i start xss-lock manually it works as expected.
i3 config:
exec --no-statup-id xss-lock -n /usr/lib/xsecurelock/dimmer -l -- xsecurelock
i3-dump-logs
$ i3-dump-log | grep xss-lock
08/14/2019 12:45:08 AM - config_parser.c:parse_config:267 - CONFIG(line 77): # xss-lock must be running
08/14/2019 12:45:08 AM - config_parser.c:parse_config:267 - CONFIG(line 83): exec --no-statup-id xss-lock -n /usr/lib/xsecurelock/dimmer -l -- xsecurelock
08/14/2019 12:45:08 AM - auto-starting --no-statup-id xss-lock -n /usr/lib/xsecurelock/dimmer -l -- xsecurelock
08/14/2019 12:45:08 AM - executing: --no-statup-id xss-lock -n /usr/lib/xsecurelock/dimmer -l -- xsecurelock
Last edited by nikzy (2019-08-16 14:55:12)
Offline
After hours of debugging. Turns out i was missing an 'r' in --no-startup-id.
exec --no-startup-id xss-lock -n /usr/lib/xsecurelock/dimmer -l -- xsecurelock
Offline