On Sun, 16 Jul 2023, at 10:56, Ian Campbell wrote:
> Hi Nikolaus,
>
> Thanks for your report.
>
> On Wed, 2023-07-12 at 18:38 +0100, Nikolaus Rath wrote:
>> It seems that running xss-lock as `xss-lock --
>> session=${XDG_SESSION_ID}` works around this problem.
>
> That's correct, you either need a working logind session (which your
> "Error getting session" suggests you either don't or you are launching
> xss-lock in a way which doesn't find it properly) or you must use this
> option to tell xss-lock the session.
I believe I have a working logind session:
nikratio@vostro ~ [1]> loginctl
SESSION UID USER SEAT TTY
2 1000 nikratio seat0 tty2
1 sessions listed.
nikratio@vostro ~> echo $XDG_SESSION_ID
2
Is this the right way to test for a "working logind"? If not, can you tell me
how to test for it?
Best,
-Nikolaus
