Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Screensaver (ttfx 120fps fullscreen) causes sustained high CPU, heat and fan noise
Reported by henrique-simoes · filed Sep 26, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
Dell Inspiron 5537, i7-4500U (Haswell 2C/4T), Intel HD 4400 + AMD Sun XT, 1920x1080@120 (HDMI), Omarchy 4.0.4-1, Hyprland 0.56.2, kernel 7.2.5-3-omarchy, ttfx 0.3.2-1, power profile performance, AC online
What's wrong?
After idle.screensaver (150s) fires, the screensaver pins a CPU core, the chassis heats up and fans ramp. Stops when the screensaver is dismissed (pkill -x ttfx).
Expected: an idle screensaver should be power-light (capped frame rate and/or a blank-only low-power mode).
Steps to recreate:
1. Set idle.screensaver to 150, stay idle 150s+ on AC with power profile performance.
2. While org.omarchy.screensaver is fullscreen, run top -b -n1 and sensors.
Observed (1x 1920x1080@120):
- foot (screensaver terminal): 62-72% CPU continuous; ttfx ~6-10%
- System %Cpu: ~7% us -> 23-30% us; load average 1.17 -> 2.70
- Package temp +58C -> +61-62C, fan ~3900/4800 RPM; drops after killing ttfx
- Baseline already warm at idle (58C / 3900 RPM), so the extra load is audible
Root cause (packaged code, no user override exists):
- bin/omarchy-screensaver hardcodes ttfx ... --frame-rate 120 --canvas-width 0 --canvas-height 0 --reuse-canvas ... --random-effect in a while true loop (only occurrence of frame-rate in /usr/share/omarchy)
- omarchy-launch-screensaver spawns one fullscreen terminal per monitor
- No env var, config key, or flag adjusts the frame rate
Possibly related: #11919 (general heat reports on performance profile).
omarchy-debug (sanitized excerpt, hardware/software only - full log available on request):
Omarchy Package: omarchy 4.0.4-1
Kernel: 7.2.5-3-omarchy x86_64
Desktop: Hyprland v0.56.2 / SDDM / Distro Omarchy
CPU: Intel Core i7-4500U (Haswell, 2 cores / 4 threads)
Graphics Device-1: Intel Haswell-ULT Integrated Graphics, driver i915
Graphics Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M], driver amdgpu
Display: Wayland, Hyprland v0.56.2, Monitor HDMI-A-1 1920x1080@120
Power profile: performance, AC online
ttfx: 0.3.2-1Suggestions (for maintainers): lower the default frame rate (e.g. 30), expose screensaver.frameRate in shell.json, and/or offer a blank-only low-power mode for always-on machines.
View raw text
### System details Dell Inspiron 5537, i7-4500U (Haswell 2C/4T), Intel HD 4400 + AMD Sun XT, 1920x1080@120 (HDMI), Omarchy 4.0.4-1, Hyprland 0.56.2, kernel 7.2.5-3-omarchy, ttfx 0.3.2-1, power profile performance, AC online ### What's wrong? After `idle.screensaver` (150s) fires, the screensaver pins a CPU core, the chassis heats up and fans ramp. Stops when the screensaver is dismissed (`pkill -x ttfx`). Expected: an idle screensaver should be power-light (capped frame rate and/or a blank-only low-power mode). Steps to recreate: 1. Set `idle.screensaver` to 150, stay idle 150s+ on AC with power profile `performance`. 2. While `org.omarchy.screensaver` is fullscreen, run `top -b -n1` and `sensors`. Observed (1x 1920x1080@120): - `foot` (screensaver terminal): 62-72% CPU continuous; `ttfx` ~6-10% - System `%Cpu`: ~7% us -> 23-30% us; load average 1.17 -> 2.70 - Package temp +58C -> +61-62C, fan ~3900/4800 RPM; drops after killing `ttfx` - Baseline already warm at idle (58C / 3900 RPM), so the extra load is audible Root cause (packaged code, no user override exists): - `bin/omarchy-screensaver` hardcodes `ttfx ... --frame-rate 120 --canvas-width 0 --canvas-height 0 --reuse-canvas ... --random-effect` in a `while true` loop (only occurrence of `frame-rate` in `/usr/share/omarchy`) - `omarchy-launch-screensaver` spawns one fullscreen terminal per monitor - No env var, config key, or flag adjusts the frame rate Possibly related: #11919 (general heat reports on performance profile). `omarchy-debug` (sanitized excerpt, hardware/software only - full log available on request): ``` Omarchy Package: omarchy 4.0.4-1 Kernel: 7.2.5-3-omarchy x86_64 Desktop: Hyprland v0.56.2 / SDDM / Distro Omarchy CPU: Intel Core i7-4500U (Haswell, 2 cores / 4 threads) Graphics Device-1: Intel Haswell-ULT Integrated Graphics, driver i915 Graphics Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M], driver amdgpu Display: Wayland, Hyprland v0.56.2, Monitor HDMI-A-1 1920x1080@120 Power profile: performance, AC online ttfx: 0.3.2-1 ``` Suggestions (for maintainers): lower the default frame rate (e.g. 30), expose `screensaver.frameRate` in `shell.json`, and/or offer a blank-only low-power mode for always-on machines.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 18:30 UTC