User services are started for the greeter user

Description:

User services are started for the greeter user.

Somehow systemd is launching user services for this particular user (I'm not an expert on this).

This is annoying as it clutters the journal with logs that usually say "unable to read/write /.config/foo/bar".

This user has / as its home:

$ cat /etc/passwd|grep greetd
greeter:x:976:976:greetd greeter user:/:/usr/bin/bash

I remember when this package was in the AUR, someone there suggested workaround which was to set greeter's home to something like /var/lib/greeter which gets rid of the annoying logs.

However, I don't think that solution is ideal. User services shouldn't even be started for greeter in the first place.

Additional info:

I'm using greetd with gtkgreet.

Here's some example logs:

Sep 19 17:46:37 terra wireplumber[869]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Sep 19 17:46:37 terra xdg-desktop-por[841]: Realtime error: Could not get pidns for pid 869: Could not fstatat ns/pid: Not a directory
Sep 19 17:46:37 terra wireplumber[869]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Sep 19 17:46:37 terra wireplumber[869]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Sep 19 17:46:37 terra wireplumber[869]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Sep 19 17:46:37 terra wireplumber[869]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied
Sep 19 17:46:37 terra wireplumber[869]: wp-state: failed to create directory /.local/state/wireplumber: Permission denied

• package version(s): 0.10.3-1
• config and/or log files:
• link to upstream bug report, if any:

Steps to reproduce:

1. Start the system with greetd.service enabled and configured to use gtkgreet.
2. Observe logs using journalctl -b 0