From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: muradm <mail@muradm.net>, 56690@debbugs.gnu.org
Subject: [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group.
Date: Mon, 08 Aug 2022 10:12:51 +0100 [thread overview]
Message-ID: <CM0J5LA0SDT1.29QEUPBP5V7JK@guix-aspire> (raw)
In-Reply-To: <87sfm7az76.fsf@gnu.org>
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
> functionality?
I don't believe there are system tests for greetd, no. There is
a bug report, though: <https://issues.guix.gnu.org/56971>.
> 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.
So the problem is some greeters try to talk to seatd, but since they
don't have the right permissions, they bail out.
-- (
next prev parent reply other threads:[~2022-08-08 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 4:27 [bug#56690] [PATCH] gnu: seatd-service-type: Should use seat group muradm
2022-07-24 16:28 ` ( via Guix-patches via
2022-08-05 8:10 ` Liliana Marie Prikler
2022-08-07 20:45 ` muradm
2022-08-06 20:46 ` Ludovic Courtès
2022-08-06 20:50 ` ( via Guix-patches via
2022-08-08 8:58 ` Ludovic Courtès
2022-08-08 9:12 ` ( via Guix-patches via [this message]
2022-08-08 19:44 ` muradm
2022-08-08 18:55 ` muradm
2022-08-07 17:28 ` muradm
2022-08-07 20:05 ` muradm
2022-08-08 6:08 ` Liliana Marie Prikler
2022-08-08 18:50 ` muradm
2022-08-09 6:57 ` Liliana Marie Prikler
2022-08-09 19:47 ` muradm
2022-08-10 8:07 ` Liliana Marie Prikler
2022-08-13 17:39 ` muradm
2022-08-22 20:17 ` muradm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CM0J5LA0SDT1.29QEUPBP5V7JK@guix-aspire \
--to=guix-patches@gnu.org \
--cc=56690@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mail@muradm.net \
--cc=paren@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).