Package Details: greetd 0.8.0-1

Git Clone URL: https://aur.archlinux.org/greetd.git (read-only, click to copy)
Package Base: greetd
Description: Generic greeter daemon
Upstream URL: https://git.sr.ht/~kennylevinsen/greetd
Licenses: GPL3
Submitter: 1ace
Maintainer: 1ace (kennylevinsen)
Last Packager: kennylevinsen
Votes: 48
Popularity: 7.29
First Submitted: 2020-04-30 23:10 (UTC)
Last Updated: 2021-09-11 14:05 (UTC)

Latest Comments

whynothugo commented on 2022-05-10 09:37 (UTC)

@somini I think you should suggest these changes upstream. They make sense to me, but I don't think an Arch package should override the upstream configuration like this.

somini commented on 2022-05-09 23:34 (UTC)

This "greeter" user should have a real home directory (/var/lib/greeter). That way, it is possible to configure the user itself using usual tools. My main concern is really configuring GTK dark mode, like this:

# cat ~/.config/gtk-3.0/settings.ini
[Settings]
gtk-application-prefer-dark-theme = true

Since the "greeter" home directory is /, this is impossible.


This can be done by creating a file in /usr/lib/tmpfiles.d/greeter.conf

#Type Path Mode User Group Age Argument
d %S/greeter 0755 greeter greeter - -

and changing the sysusers configuration to:

u greeter - "greetd greeter user" /var/lib/greeter /bin/bash

This defines the home directory in /var/lib/greeter, but it can also be /etc/greetd/home, for example.

whynothugo commented on 2022-05-01 15:16 (UTC)

@itaranto Odd, I see no systemd user instance for the greetd user.

Are you sure this is caused by greetd itself and not the greeter? Which one are you using? Can you try using agreety and see if you have the same issue?

Also, do you see the systemd service when grepping like this?

$ ps aux | grep greet
root         893  0.0  0.0   3716  3688 ?        SLs  14:41   0:00 greetd
root         894  0.0  0.0   8580  8552 tty1     SLs+ 14:41   0:00 /usr/bin/greetd --session-worker 11
hugo       29849  0.0  0.0   7012  2680 pts/3    S+   17:16   0:00 grep --color=auto --exclude-dir=.git greet

itaranto commented on 2022-04-30 14:34 (UTC) (edited on 2022-04-30 14:35 (UTC) by itaranto)

There are no "real" users, just users. The greeter runs in a session for the "greeter" user to limit privileges. On a systemd system, in order to be able to run a graphical environment, logind needs to register the login properly to grant I/O access. This also starts a (harmless) systemd user service manager.

This is all entirely unrelated to xdg-desktop-portal starting. This is a dbus activated service, which starts only because Gtk is talking to it.

Sorry to bring this topic again, but I'm trying to prevent systemd from starting user services for greeter since I want to prevent silly error messages like the following:

Apr 30 10:26:32 terra wireplumber[745]: failed to create directory /.local/state/wireplumber: Permission denied

which arise from the fact that greeter's home directory is / since it's a sysuser.

How can I prevent systemd launching user services for greeter?
Should this fix be included in this package?

whynothugo commented on 2022-03-22 13:23 (UTC)

This works fine on aarch64 for me. Can add this to the PKGBUILD? arch=(x86_64 aarch64)

connaisseur commented on 2022-02-20 07:47 (UTC) (edited on 2022-02-20 07:54 (UTC) by connaisseur)

As a suggestion I've made a patch to PKGBUILD - for a more fancier, slicker way of the greeter user id. As a plus this provides an install file. Just to have a CLEAN system in case a user as no use for greetd anymore.

See: https://pastebin.com/9yLKYsBH

dpirate commented on 2022-01-27 14:37 (UTC)

Hi,

I noticed the man pages were installed with 755 perms, that should be 644.

brodi1 commented on 2021-10-09 19:26 (UTC) (edited on 2021-10-09 19:26 (UTC) by brodi1)

error in build()

error: no override and no default toolchain set

TrialnError commented on 2021-08-12 18:11 (UTC)

To make life easier for people which set makepkg's SRCDEST to a common location, would it be possible to add ${pkgname}-${pkgver}.tar.gz:: in front of the source url which links to the tarball?
Thanks in advance

kennylevinsen commented on 2021-06-03 20:13 (UTC)

In my opinion, the greeter user shouldn't spawn systemd user services which are intended for real users. Don't you agree?

There are no "real" users, just users. The greeter runs in a session for the "greeter" user to limit privileges. On a systemd system, in order to be able to run a graphical environment, logind needs to register the login properly to grant I/O access. This also starts a (harmless) systemd user service manager.

This is all entirely unrelated to xdg-desktop-portal starting. This is a dbus activated service, which starts only because Gtk is talking to it.

itaranto commented on 2021-05-30 14:37 (UTC) (edited on 2021-05-30 14:39 (UTC) by itaranto)

Report xdg-desktop-portal-wlr crashes to upstream.

Will do.

greetd usually launches your greeter as the "greeter" user, yes. systemd-logind eavesdrops on this through PAM and starts a user service manager for the session.

I've been using Linux for more than 10 years and I still haven't learnt how PAM/systemd works :/

In my opinion, the greeter user shouldn't spawn systemd user services which are intended for real users. Don't you agree?

kennylevinsen commented on 2021-05-25 17:08 (UTC)

greetd usually launches your greeter as the "greeter" user, yes. systemd-logind eavesdrops on this through PAM and starts a user service manager for the session.

Report xdg-desktop-portal-wlr crashes to upstream.

re: rustup, I don't think it's a good idea to mess around with the default toolchain. That's user configuration, and setting up defaults of another package is not our job.

rustup is allowed so that rust developers, who often use rustup, can use their existing toolchain instead of having to install an entirely separate one just for building the package. If you don't code in rust, just use the normal rust packages.

itaranto commented on 2021-05-25 14:44 (UTC)

It seems that greetd is lauching a systemd user session with the "greeter" user. Is this intended?

Right now it's making xdg-desktop-portal-wlr to crash for some reason. I'm using sway + greetd-gtkgreet.

carsme commented on 2021-05-25 00:20 (UTC)

Had the same issue as @maroider on a freshly installed system due to no default rustup toolchain being set yet.

Setting the toolchain when building seems like something that should be added to the PKGBUILD.

abouvier commented on 2021-03-15 15:52 (UTC)

arch=(any) is for architecture independent package. You can't set that for a package providing compiled binaries.

thurstylark commented on 2021-03-10 00:06 (UTC)

Is there any reason to keep this package set to x86_64?

kennylevinsen commented on 2021-02-11 08:45 (UTC)

sha256sum fixed - a sourcehut upgrade had caused the tarball to change slightly.

xisberto commented on 2021-02-10 22:18 (UTC)

The sha256sum of the tar.gz package isn't matching the one in the PKGBUILD.

3KyNoX commented on 2020-11-19 20:50 (UTC)

Hello!

Is there any way to change the keymap? I'm stuck at login with qwerty keyboard and I would like to switch to french azerty one. I find nothing around about that...

Thanks anyway.

maroider commented on 2020-07-28 15:04 (UTC) (edited on 2020-07-28 15:09 (UTC) by maroider)

I had some trouble installing this with rua and ended up having to add RUSTUP_TOOLCHAIN="stable" in front of RUSTFLAGS="--remap-path-prefix=$(pwd)=/build/" cargo build --release --locked. This may or may not be related to rustup being installed instead of rust.