Package: greetd
Version: 0.10.3-5
Severity: minor
Hello,
thanks for maintaining greetd. I tried using it to autologin a user with
sway. This can be sensible e.g. when using full disk encryption or when
using greetd to implement a kiosk-style system. I am observing that
greetd is started relatively early. At least rtkit and dbus-broker are
started after greetd spawns sway. In the end the login session fails
(with no clear indication why).
If I later remove /run/greetd.run, and systemctl restart greetd,
autologin reliably works.
Once I added After=basic.target to greetd.service, I did not observe
failed logins anymore.
I recognize that autologin is a non-default configuration and that the
problem likely does not affect typical prompters such as agreety nor its
default configuration.
How do we want to move from here?
1. Declare not-a-bug. If I reconfigue greetd to launch a payload that
requires further service, it is my responsibility to declare them.
2. Find out what services are typically required and list them
explicitly in the systemd unit. (How?)
3. Declare After=basic.target. This may defer the presentation of the
greeter more than necessary, but for me it was hardly noticeable. It
also saves us from figuring out what the correct dependency is.
If you choose 1, please tag wontfix and close.
Helmut
