Skip to content

Conversation

SoumyaRanjanPatnaik
Copy link
Contributor

@SoumyaRanjanPatnaik SoumyaRanjanPatnaik commented Aug 23, 2025

Currently the lock program doesn't work across the wayland and x11 sessions. This is a challenge since most locking software only supports one of the ecosystems.

BREAKING CHANGE: This PR splits the XResource key wm.program.lock for the lock program into wm.program.lock_sway and wm.program.lock_i3.

NOTE: This change may require a change in documentation

FIXES: regolith-linux/regolith-powerd#3

@SoumyaRanjanPatnaik SoumyaRanjanPatnaik force-pushed the chore/seperate-keys-for-lock-program branch from f77214f to fe8b80d Compare August 23, 2025 05:40
Copy link
Member

@kgilmer kgilmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for next release

@kgilmer
Copy link
Member

kgilmer commented Aug 23, 2025

I guess another way we could have modeled WM variance (i3/sway) would have been to specify distinct roots for i3 and sway XResource roots. Unsure of the relative pros/cons over the path we choose.

@SoumyaRanjanPatnaik
Copy link
Contributor Author

SoumyaRanjanPatnaik commented Aug 23, 2025

I thought of that actually. That's the original solution that we though of in the issue (see this comment). But it seemed inconsistent with the convention we've been following.

@SoumyaRanjanPatnaik
Copy link
Contributor Author

I actually couldn't find a single other instance where sway and i3 would require different resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changing wm.program.lock doesn't apply on suspend
2 participants