OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend low occasional DISPUTE

Stop the Omarchy screensaver pinning a CPU core and spinning up the fans

omarchyhyprlandlaptopdesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Cause matches issue #13279 (open) and the installed omarchy-screensaver, which is byte-identical to quattro: ttfx ... --frame-rate 120 in a loop with no override. omarchy toggle screensaver resolves (longest-prefix route) to omarchy-toggle-screensaver, which flips ~/.local/state/omarchy/toggles/screensaver-off. omarchy-launch-screensaver exits 1 when that flag is set. In Service.qml the lock timer is independent of the screensaver launching, and the launch-grace timer does not cancel the cycle while the monitor is still idle, so the lock still fires at idle.lock. Two defects. First, the menu path: omarchy-menu.jsonc has it at trigger.toggle.screensaver, Trigger > Toggle > Screensaver, not 'Toggle, Screensaver'. Second, the symptom names foot as the screensaver terminal, which was only that reporter's default. omarchy-launch-screensaver uses the default terminal and supports Alacritty, Foot, Ghostty and Kitty.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

When the machine goes idle the Omarchy screensaver comes up and the fans ramp. top shows the screensaver's terminal (Alacritty, foot, Ghostty or Kitty, whichever is your default) using most of a CPU core, 60-70% in the original report, and ttfx at 6-10% for as long as it runs. Temperatures and fan speed drop as soon as I dismiss it or run pkill -x ttfx.

Cause

/usr/share/omarchy/bin/omarchy-screensaver runs ttfx at a hardcoded --frame-rate 120 in a loop, and omarchy-launch-screensaver opens one fullscreen terminal per monitor. Rendering text effects at 120 frames per second in a terminal costs real CPU on older or low-power CPUs. No config key, environment variable or flag changes the frame rate (open issue, 4.0.4-1).

Fix

Turn the screensaver off and keep the idle lock. Use the Super+Space menu (Trigger > Toggle > Screensaver), or:


omarchy toggle screensaver

This touches ~/.local/state/omarchy/toggles/screensaver-off, which omarchy-launch-screensaver checks before starting. The idle lock still fires at idle.lock (300 seconds by default). Run the same command again to turn the screensaver back on.

Do not edit /usr/share/omarchy/bin/omarchy-screensaver. It is package-owned and the next omarchy update overwrites it.

If the fans are loud even without the screensaver, check the power profile first (see omarchy-performance-profile-fans-max-on-ac).

Verify

ls ~/.local/state/omarchy/toggles/screensaver-off exists. After idle.screensaver seconds no ttfx process appears (pgrep -x ttfx prints nothing), and the session still locks at idle.lock.

Sources

omarchy-screensaver-high-cpu-heat-fan-noise