From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: 75270@debbugs.gnu.org
Subject: [bug#75270] Fwd: [bug#75270] [PATCH 1/3] services: greetd: Improve greeter configurations.
Date: Sat, 04 Jan 2025 17:14:32 +0100 [thread overview]
Message-ID: <87a5c61rpz.fsf@ngraves.fr> (raw)
In-Reply-To: <cover.1735771462.git.mail@muradm.net>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
-------------------- Start of forwarded message --------------------
From: muradm <mail@muradm.net>
To: Nicolas Graves <ngraves@ngraves.fr>
Subject: Re: [bug#75270] [PATCH 1/3] services: greetd: Improve greeter
configurations.
Date: Sat, 04 Jan 2025 16:49:09 +0300
[-- Attachment #2.1: Type: text/plain, Size: 2959 bytes --]
Nicolas Graves <ngraves@ngraves.fr> writes:
> On 2025-01-04 11:57, Nicolas Graves wrote:
>
>>> When you start sway, it has to put WAYLAND_DISPLAY somewhere.
>>> By
>>> default it is put to `/run/user/<uid>`. However greeter is
>>> special
>>> limited user which is used to run without logging in. Because
>>> of
>>> that, `/run/user/<uid>` is not created by PAM mount. For
>>> special
>>> purpose we can use any XDG_RUNTIME_DIR. Sway does not support
>>> specifying location of WAYLAND_DISPLAY as far as I remember (I
>>> was
>>> opening an issue about it long ago, still was not resolved).
>>
>> IIUC, it's because of PAM mount execution order that this
>> happens? So
>> there's also no need for that for people that don't use PAM
>> mount.
>> Maybe completing the comment as "/run/user/<greeter-user-uid>
>> won't
>> exist yet due to PAM mount execution order" comment would make
>> that
>> clearer?
>>
>> Is the logfile here the one logging everything Sway? Could you
>> make the
>> logfile configurable or is that not possible due to
>> unguaranteed dir
>> existence due to PAM mount? We are making an extra effort to
>> locate
>> logfiles in the same dir in RDE. (I could also try and make a
>> symlink a
>> posteriori to the right dir).
>
> Actually, I'm not sure I understand properly.
>
> I use agreety, then sway through ~/.profile because default is
> bash
> --login.
This is most straightforward and IMHO correct way to start
whatever user wants.
> It works OK, because the user (not greetd) launches Sway.
> Should I care about your changes ?
No, you should not care about stuff happening in script in
`make-greetd-sway-greeter-command`. User session is started by
scripts within `make-greetd-user-session-command` and
`make-greetd-xdg-user-session-command`. Where user session command
is specified by `command`, `command-args` and `extra-env` in
`<greetd-user-session>`.
Most notable impact of this change, as noted in cover letter is
that user session now factored out. Now you are able to pass
instance of `<greetd-user-session>` to any properly defined
greeter, which are agreety, wlgreet and gtkgreet as of this
change.
I'm not RDE or guix home user, but I suppose that their entry
point should be an instance of `<greetd-user-session>` or
combination of greeter and `<greetd-user-session>`.
> If I want to skip this bash step and make greetd launch sway
> directly,
> then I would need this script, otherwise, it is not necessary,
> am I
> right? Is there any upside / reason I should switch?
Technically, you may set `command`, `command-args` and `extra-env`
to sway, its required arguments and if necessary environment
variables of `<greetd-user-session>` instance, carefully
considering `xdg-env?` and `xdg-session-type`. But, as I mentioned
above, IMHO and from my experience, starting from
.bashrc/.profile/whatever from user home and editable by user is
more correct and straightforward.
[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #3: Type: text/plain, Size: 101 bytes --]
-------------------- End of forwarded message --------------------
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2025-01-04 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87jzbar8oa.fsf@muradm.net>
2025-01-01 22:47 ` [bug#75270] [PATCH 0/3] services: greetd: Improve greeter configurations muradm
2025-01-01 22:53 ` [bug#75270] [PATCH 1/3] " muradm
2025-01-03 13:23 ` Nicolas Graves via Guix-patches via
2025-01-03 17:08 ` muradm
2025-01-04 10:57 ` Nicolas Graves via Guix-patches via
2025-01-04 13:36 ` muradm
2025-01-01 22:53 ` [bug#75270] [PATCH 2/3] gnu: Add gtkgreet muradm
2025-01-01 22:53 ` [bug#75270] [PATCH 3/3] services: greetd: Add new gtkgreet greeter muradm
2025-01-03 11:34 ` [bug#75270] [PATCH 0/3] services: greetd: Improve greeter configurations muradm
2025-01-04 16:14 ` Nicolas Graves via Guix-patches via [this message]
2025-01-04 16:58 ` [bug#75270] [PATCH v2 " muradm
2025-01-04 16:58 ` [bug#75270] [PATCH v2 1/3] " muradm
2025-01-04 16:58 ` [bug#75270] [PATCH v2 2/3] gnu: Add gtkgreet muradm
2025-01-04 16:58 ` [bug#75270] [PATCH v2 3/3] services: greetd: Add new gtkgreet greeter 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=87a5c61rpz.fsf@ngraves.fr \
--to=guix-patches@gnu.org \
--cc=75270@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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).