Make the screensaver engage properly when idle - #8738
Closed
pablohc wants to merge 2 commits into
Closed
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-Authored-By: Claude <noreply@anthropic.com>
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
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.
What was broken
Two stacked bugs kept the screensaver from ever engaging:
omarchy-launch-screensaverends withhypr_focus_monitor "$focused", restoring focus to the previously focused window.omarchy-screensaverexits whenever it is not the active window (hyprctl activewindowclass check), so the launcher's own last line killed the screensaver it just launched — leaving a windowed flash instead of a screensaver, on every idle cycle. Because each death looked like a user dismissal, the idle service canceled the pending lock timer too, so the screen also never locked.Fixes
Commit 1 — keep focus on the screensaver after launching it: iterate monitors with the focused one last and drop the final focus restore. The last spawned screensaver (on the user's own monitor) keeps focus, which preserves the intent of ending on the user's monitor — and since every screensaver terminal shares the
org.omarchy.screensaverclass, the active-window check passes for all of them.Commit 2 — close open panels before the screensaver takes over:
startIdleCycle()now closes the bar's active popout and any summoned panels (menu, emojis, clipboard, ...) before launching the screensaver, via the newIdleModel.openPanelIdsToClosehelper. Each closure is logged asclose-open-panelfor diagnostics.Verification
On a single-monitor (eDP-1, foot) machine:
close-open-panel: bar popoutin the idle journal) and the screensaver engages fullscreen with nothing drawn on top.test/shell.d/idle-test.shextended with coverage foropenPanelIdsToCloseand passing;./test/clipasses. Three shell-suite failures (config-test,snapper-test,unowned-system-paths-test) are pre-existing on this machine and unrelated to this change — e.g. "omarchy-pkgs checkout found for PKGBUILD coverage" fails for lack of a local checkout.🤖 Generated with Claude Code