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 is broken after 3.2.0 update
Reported by marionuevo · filed Nov 22, 2025Closed upstream on 2025-11-22 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
i7-10700K RTX3090 Omarchy 3.2.0
What's wrong?
It looks like a recent update in tte broke the omarchy screensaver. Executing tte from the terminal with the parameters shown in omarchy-cmd-screesaver shows:
~ ❯ tte -i ~/.config/omarchy/branding/screensaver.txt \
--frame-rate 120 --canvas-width 0 --canvas-height 0 --anchor-canvas c --anchor-text c\
--no-eol --no-restore-cursor random_effect
usage: tte [-h] [--input-file INPUT_FILE] [--version] [--tab-width (int > 0)] [--xterm-colors] [--no-color] [--existing-color-handling {always,dynamic,ignore}]
[--wrap-text] [--frame-rate FRAME_RATE] [--canvas-width int >= -1] [--canvas-height int >= -1] [--anchor-canvas {sw,s,se,e,ne,n,nw,w,c}]
[--anchor-text {n,ne,e,se,s,sw,w,nw,c}] [--ignore-terminal-dimensions] [--no-eol]
{beams,binarypath,blackhole,bouncyballs,bubbles,burn,colorshift,crumble,decrypt,errorcorrect,expand,fireworks,highlight,laseretch,matrix,middleout,orbittingvolley,overflow,pour,print,rain,randomsequence,rings,scattered,slice,slide,spotlights,spray,swarm,sweep,synthgrid,unstable,vhstape,waves,wipe} ...
tte: error: argument {beams,binarypath,blackhole,bouncyballs,bubbles,burn,colorshift,crumble,decrypt,errorcorrect,expand,fireworks,highlight,laseretch,matrix,middleout,orbittingvolley,overflow,pour,print,rain,randomsequence,rings,scattered,slice,slide,spotlights,spray,swarm,sweep,synthgrid,unstable,vhstape,waves,wipe}: invalid choice: 'random_effect' (choose from beams, binarypath, blackhole, bouncyballs, bubbles, burn, colorshift, crumble, decrypt, errorcorrect, expand, fireworks, highlight, laseretch, matrix, middleout, orbittingvolley, overflow, pour, print, rain, randomsequence, rings, scattered, slice, slide, spotlights, spray, swarm, sweep, synthgrid, unstable, vhstape, waves, wipe)It looks like the random_effect mode is no longer valid. Also, I tried changing it to randomsequence, but then it shows:
tte: error: unrecognized arguments: --no-restore-cursorView raw text
### System details
i7-10700K RTX3090 Omarchy 3.2.0
### What's wrong?
It looks like a recent update in **tte** broke the omarchy screensaver. Executing **tte** from the terminal with the parameters shown in **omarchy-cmd-screesaver** shows:
```
~ ❯ tte -i ~/.config/omarchy/branding/screensaver.txt \
--frame-rate 120 --canvas-width 0 --canvas-height 0 --anchor-canvas c --anchor-text c\
--no-eol --no-restore-cursor random_effect
usage: tte [-h] [--input-file INPUT_FILE] [--version] [--tab-width (int > 0)] [--xterm-colors] [--no-color] [--existing-color-handling {always,dynamic,ignore}]
[--wrap-text] [--frame-rate FRAME_RATE] [--canvas-width int >= -1] [--canvas-height int >= -1] [--anchor-canvas {sw,s,se,e,ne,n,nw,w,c}]
[--anchor-text {n,ne,e,se,s,sw,w,nw,c}] [--ignore-terminal-dimensions] [--no-eol]
{beams,binarypath,blackhole,bouncyballs,bubbles,burn,colorshift,crumble,decrypt,errorcorrect,expand,fireworks,highlight,laseretch,matrix,middleout,orbittingvolley,overflow,pour,print,rain,randomsequence,rings,scattered,slice,slide,spotlights,spray,swarm,sweep,synthgrid,unstable,vhstape,waves,wipe} ...
tte: error: argument {beams,binarypath,blackhole,bouncyballs,bubbles,burn,colorshift,crumble,decrypt,errorcorrect,expand,fireworks,highlight,laseretch,matrix,middleout,orbittingvolley,overflow,pour,print,rain,randomsequence,rings,scattered,slice,slide,spotlights,spray,swarm,sweep,synthgrid,unstable,vhstape,waves,wipe}: invalid choice: 'random_effect' (choose from beams, binarypath, blackhole, bouncyballs, bubbles, burn, colorshift, crumble, decrypt, errorcorrect, expand, fireworks, highlight, laseretch, matrix, middleout, orbittingvolley, overflow, pour, print, rain, randomsequence, rings, scattered, slice, slide, spotlights, spray, swarm, sweep, synthgrid, unstable, vhstape, waves, wipe)
```
It looks like the **random_effect** mode is no longer valid. Also, I tried changing it to **randomsequence**, but then it shows:
```
tte: error: unrecognized arguments: --no-restore-cursor
```
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.
No decision has been recorded yet.