From: furryfixer <furryfixer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Greetd unable to login & elogind error
Date: Mon, 04 Apr 2022 03:53:13 +0200 [thread overview]
Message-ID: <20220404015313.hcxmwlpQZDW33Z4D57x5rGW0Mck04_7lMAjbpYz3ZK4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35870@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
New comment by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/35870#issuecomment-1087029897
Comment:
Probably not the same as #195 (I may comment there as well). Void's `greetd` installation is slightly broken, in that no default shell is assigned to the `_greeter` user, or `$SHELL="/sbin/nologin"`. Arch at least assigns "/bin/bash" as shell for the greeter user. Greetd references the "$SHELL" variable in `/etc/greetd/config.toml`. Users often replace $SHELL with something else, accidentally eliminating the bug.
The easiest solution is to:
`sudo chsh -s /bin/bash _greeter`
or you may edit `/etc/greetd/config.toml` as root, changing `$SHELL` to `/bin/bash` or whatever you prefer. Alternatively, you may also create a default `SHELL="/bin/bash"` in `/etc/environment`.
next prev parent reply other threads:[~2022-04-04 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 1:16 [ISSUE] " RicArch97
2022-02-28 12:30 ` travankor
2022-04-04 1:53 ` furryfixer [this message]
2022-04-07 2:45 ` cinerea0
2022-04-07 3:31 ` RicArch97
2022-04-07 20:29 ` cinerea0
2022-04-07 21:04 ` furryfixer
2022-04-11 15:01 ` [ISSUE] [CLOSED] " paper42
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220404015313.hcxmwlpQZDW33Z4D57x5rGW0Mck04_7lMAjbpYz3ZK4@z \
--to=furryfixer@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).