service/greetd: always send responses #223
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
outfoxxed
force-pushed
the
master
branch
2 times, most recently
from
e170d91 to
1d94144
Compare
outfoxxed
force-pushed
the
fix/greetd-responses
branch
from
1459868 to
2d9b664
Compare
outfoxxed
approved these changes
Sep 30, 2025
outfoxxed
force-pushed
the
fix/greetd-responses
branch
from
2d9b664 to
f12f0e7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I use the greetd service with a pam configuration that allows logging in with fprintd.
Since on master the greetd session blocks after the pam fprintd messages a prompt to touch the scanner and greetd relays it to quickshell, it appears to me that greetd expects every message to be acknowledged even if no text response is required.