Skip to content

Cap the screensaver frame rate and make it configurable - #10467

Closed
Eric-Fernald wants to merge 1 commit into
omacom:quattrofrom
Eric-Fernald:screensaver-frame-rate
Closed

Eric-Fernald wants to merge 1 commit into
omacom:quattrofrom
Eric-Fernald:screensaver-frame-rate

Conversation

@Eric-Fernald

@Eric-Fernald Eric-Fernald commented Sep 6, 2026 •

Copy link
Copy Markdown

Problem

omarchy-screensaver hardcoded --frame-rate 120 for ttfx. The screensaver terminal (foot by default) rasterizes every frame on the CPU at native panel resolution, so on HiDPI displays that pinned several cores and thermally throttled the machine. On QXL VMs it exhausted video memory.

Most of those frames were wasted anyway, since the panels refresh at 60Hz.

Fix

  • Default to 60fps instead of 120.
  • Cap each screensaver window to its monitor's refresh rate. omarchy-launch-screensaver reads the rate from hyprctl monitors and passes it as OMARCHY_SCREENSAVER_MAX_FRAME_RATE.
  • Make the rate configurable. The new omarchy-screensaver-frame-rate helper resolves idle.screensaverFrameRate from shell.json, so the rate can be lowered further without editing package-owned files.

Testing

  • New test/shell.d/screensaver-frame-rate-test.sh covers the default, config reads, invalid values, broken JSON, refresh-rate capping, and the wiring through both scripts.
  • omarchy commands --check passes with the new hidden helper registered.

Relationship to PR #8556

#8556 makes the frame rate overridable via OMARCHY_SCREENSAVER_FRAME_RATE but keeps 120 as the default, so affected machines still hit the problem until the user finds the variable. This PR changes the default: 60fps capped to the monitor's real refresh rate, since ttfx frames above that are discarded by the compositor. That fixes #9193 and #8554 for everyone without configuration, and puts the override in shell.json alongside the other idle settings rather than in UWSM env. Happy to add the env var as an additional override if that's preferred.

Fixes #9193
Fixes #8554

omarchy-screensaver hardcoded --frame-rate 120 for ttfx. The screensaver
terminal (foot by default) rasterizes every frame on the CPU at native
panel resolution, so on HiDPI displays that pinned several cores and
thermally throttled the machine; on QXL VMs it exhausted video memory.
Most of those frames were wasted anyway, since the panels refresh at 60Hz.

Default to 60fps and cap each screensaver window to its monitor's refresh
rate: omarchy-launch-screensaver passes the rate from hyprctl monitors as
OMARCHY_SCREENSAVER_MAX_FRAME_RATE, and the new omarchy-screensaver-frame-rate
helper resolves it against idle.screensaverFrameRate in shell.json, so the
rate can be lowered further without editing package-owned files.

Fixes omacom#9193
Fixes omacom#8554
@Eric-Fernald
Eric-Fernald deleted the screensaver-frame-rate branch September 6, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant