[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group.

From: muradm
Subject: [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group.
Date: Mon, 08 Aug 2022 22:44:37 +0300
User-agent: mu4e 1.8.7; emacs 29.0.50

"(" <> writes:

On Mon Aug 8, 2022 at 9:58 AM BST, Ludovic Courtès wrote:
Is there a bug report, and do we have system tests for this

I don't believe there are system tests for greetd, no. There is
a bug report, though: <>.

I admit I know little about greetd and cases where it might be used.

As I understand it, greetd is a daemon that handles the sensitive parts of display managers, which it calls 'greeters'. It allows you to write a login program without having to write those difficult and sensitive parts by simply writing a GUI that sends JSON messages to the socket when it
gets input.
For greetd/greeter this is fine explanation.

So the problem is some greeters try to talk to seatd, but since they
don't have the right permissions, they bail out.
To be more correct here, greeter that requires both talking to greetd and talking to seatd via libseat. Suppose gtkgreet which is running
with sway. So greetd will start greeter which is
"sway -c config-which-starts-gtkgreet.conf". Now you have two processes in the scope of greeter, one is sway which has to talk to swatd via libseat and the other is gtkgreet which is going to talk with greetd.

The one who bails out is sway here due to lack of permissions for
seatd.sock for talking to seatd via libseat.

    -- (

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]