From: muradm <mail@muradm.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Lars-Dominik Braun <lars@6xq.net>, kiasoc5 <kiasoc5@disroot.org>,
Brian Cully <bjc@spork.org>,
guix-devel@gnu.org
Subject: Re: Why is greetd greeter user in so many groups?
Date: Thu, 04 Aug 2022 13:04:26 +0300 [thread overview]
Message-ID: <878ro42ujo.fsf@muradm.net> (raw)
In-Reply-To: <878ro4pet0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Hi,
Here you are: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56971
I added explanations and proposed solution there as well.
Thanks in advance,
muradm
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> muradm <mail@muradm.net> skribis:
>
>> This change broke greetd on my side as I am using it with
>> gtkgreet.
>
> Could you open an issue so we keep track of this?
>
>> While greetd is running as root, specific greeter started by it
>> is
>> not.
>>
>> This many groups was required to:
>> - make it able starting graphical greeters with user greeter
>> - access to seatd's socket file
>
> That sounds surprising to me. If other distros don’t do that,
> there
> must be something we’re missing?
>
> Anyway, let’s see how to move forward.
>
> Thanks,
> Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2022-08-04 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 4:33 Why is greetd greeter user in so many groups? kiasoc5
2022-06-22 14:17 ` Lars-Dominik Braun
2022-06-22 14:24 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-23 10:41 ` Lars-Dominik Braun
2022-06-23 12:15 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-29 7:41 ` Lars-Dominik Braun
2022-06-29 17:59 ` kiasoc5
2022-06-30 7:48 ` Lars-Dominik Braun
2022-08-02 8:44 ` muradm
2022-08-04 8:56 ` Ludovic Courtès
2022-08-04 10:04 ` muradm [this message]
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=878ro42ujo.fsf@muradm.net \
--to=mail@muradm.net \
--cc=bjc@spork.org \
--cc=guix-devel@gnu.org \
--cc=kiasoc5@disroot.org \
--cc=lars@6xq.net \
--cc=ludo@gnu.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).