Re: Sway not locked after resume

Renato Botelho <garga@FreeBSD.org> writes:

> On 15/05/25 13:37, Gleb Popov wrote:
>
>> On Thu, May 15, 2025 at 7:04 PM Renato Botelho <garga@freebsd.org> wrote:
>>>
>>> before-sleep <command>
>>>       If built with ConsoleKit2 support, executes command before
>>>       ConsoleKit2 puts the computer to sleep.
>> So it seems that ConsoleKit should be used and I don't see any
>> mentions of it in the relevant Handbook chapter. I think plugging
>> "ck-launch-session" somewhere into the command line that starts the
>> graphical session should help.
>
> I've started sway by using `ck-launch-session sway` and confirmed
> session was created by running ck-list-sessions but it didn't help.

ck-launch-session alone isn't enough to make sway use consolekit2.
Either seatd should be stopped or LIBSEAT_BACKEND=consolekit2 set.
This is documented in "pkg info -D seatd".

ck-list-sessions output is kinda useless. You need to run sway in debug
mode (-d flag) to see whether libseat uses consolekit2 or seatd. However,
if seatd is NOT running the only way seatd backend would be used if
sway was started via seatd-launch(1).