Skip to content

Comments

Inhibit output rendering from wayfire directly instead of relying on clients#2978

Merged
ammen99 merged 1 commit intomasterfrom
core-init-inhibit
Feb 20, 2026
Merged

Inhibit output rendering from wayfire directly instead of relying on clients#2978
ammen99 merged 1 commit intomasterfrom
core-init-inhibit

Conversation

@soreau
Copy link
Member

@soreau soreau commented Feb 20, 2026

This also disables inhibiting outputs from client side, as this could lead to a black screen forever if the client does not uninhibit.

@soreau soreau force-pushed the core-init-inhibit branch 2 times, most recently from e6535fa to d420f6a Compare February 20, 2026 11:19
@soreau soreau force-pushed the core-init-inhibit branch 5 times, most recently from c1dad9f to f7be324 Compare February 20, 2026 13:04
…clients

This also disables inhibiting outputs from client side, as this could
lead to a black screen forever if the client does not uninhibit.
Copy link
Member

@ammen99 ammen99 left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@ammen99 ammen99 merged commit ad2c781 into master Feb 20, 2026
6 of 8 checks passed
soreau added a commit to WayfireWM/wf-shell that referenced this pull request Feb 21, 2026
Wayfire now handles this internally.

Reference: WayfireWM/wayfire#2978
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.

2 participants