greetd is stuck in crashloop if the user configured for initial session is locked

If pam stack returns failure for the initial session user, greetd terminates, restarts and attempts to start initial session again. That would fail again and the sequence would continue until systemd decides that it's enough.

A fix for #10 would mitigate that, but I had an expectation that the authentication failure of initial session should simply cause greetd to proceed to the default session.

Assigned to
1 year, 2 months ago
3 months ago
No labels applied.

~kennylevinsen 1 year, 2 months ago

That's a fatal configuration error. Not much greetd can do other than fail at startup. It's true that there is a special case where initial is broken but default is not, but not sure if a limb mode for that special case is that useful.

On the other hand, I wonder if we could/should return a different status code so we could interrupt the pointless restart loop...

#10 should be fixed, but that's separate.

~apognu 4 months ago

My proposed patch for #10 should also solve this issue.

~kennylevinsen REPORTED FIXED 3 months ago

Register here or Log in to comment, or comment via email.