Safer screnlock support #6483
Closed
Safer screnlock support #6483
Conversation
This file contains 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
This will always accept lock requests, including replacing a current locker if present. Based a prototype by: Manuel Stoeckl <[email protected]>
danieldg
force-pushed
the
safe-locking
branch
from
18ae63c to
2b2df8e
Compare
|
Replaced by #6879 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See swaywm/wlroots#2706 and swaywm/wlroots#3165.
We may also want to add a command to automatically run something if the lockscreen crashes. Currently you can use a
bindsym --lockedto relaunch swaylock, but that's not very obvious or user-friendly. Avoiding a crash-relaunch 100% CPU loop will be a problem with the simple solution, however.Related swaylock branch: https://github.com/danieldg/swaylock/tree/lock-protocol - no MR there yet.