On 2022-09-14 21:41:52, Antoine Beaupré wrote:
> That seems to say that this command is supposed to trigger a lock:
>
> loginctl lock-session
>
> and it does *not* work here. Does it work for you?
So, interestingly, this issue has mostly gone away from my workstations
now, after a general
Oh and I found more information about this in the arch wiki:
https://wiki.archlinux.org/title/Session_lock#xss-lock
That seems to say that this command is supposed to trigger a lock:
loginctl lock-session
and it does *not* work here. Does it work for you?
It seems the `xset s` mechanism i
On 2022-09-04 07:57:11, Ian Campbell wrote:
> On Thu, 2022-08-25 at 13:27 -0400, Antoine Beaupre wrote:
>> I have xss-lock setup to start xsecurelock automatically after the
>> delay prescribed by my `xset` configuration.
>
> FWIW I've never seen it used with xsecurelock (I use i3lock) but I do
>
On Thu, 2022-08-25 at 13:27 -0400, Antoine Beaupre wrote:
> I have xss-lock setup to start xsecurelock automatically after the
> delay prescribed by my `xset` configuration.
FWIW I've never seen it used with xsecurelock (I use i3lock) but I do
`xset b off` in my session (but not the `s 60 3`
Package: xss-lock
Version: 0.3.0-10+b1
Severity: important
I have xss-lock setup to start xsecurelock automatically after the
delay prescribed by my `xset` configuration.
Basically, I have this in my .config/systemd/user/xset.service:
[Unit]
Description=Miscellaneous settings for X11
5 matches
Mail list logo
