Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that session is relocked if compositor or lock screen die #28

Open
jackpot51 opened this issue Apr 5, 2024 · 2 comments
Open
Assignees
Milestone

Comments

@jackpot51
Copy link
Member

When #27 is merged, it will be possible to save a file to some path like /run/user/$UID/cosmic-greeter-$XDG_SESSION_ID to denote when the session is supposed to be locked. This file can be used to automatically relock the session if either the compositor or the lock screen died and were restarted.

@jackpot51 jackpot51 self-assigned this Apr 5, 2024
@jokeyrhyme
Copy link
Contributor

This might only be needed for the case that the compositor malfunctions

Provided the compositor is still functioning and implements https://wayland.app/protocols/ext-session-lock-v1 , the lock screen should be able to malfunction without the compositor considering the screen unlocked

@Drakulix
Copy link
Member

The compositor doesn't unlock the screen, but cosmic-greeter needs to know on restart (after a potential malfunction), if it should run in the background or re-acquire the lock to display the lock screen.

@WatchMkr WatchMkr added this to the alpha 2 milestone May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Alpha 2
Development

No branches or pull requests

4 participants