Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-5143GitHub issuePublicDecided· Out of scope

Enabling Stay Awake mid-idle-cycle leaves the screensaver window running indefinitely

Reported by airenare · filed Oct 4, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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

Enabling Stay Awake mid-idle-cycle leaves the screensaver window running indefinitelyrevision 1 · captured 2026-10-04 16:54 UTC via poll

What happened

The screensaver was launched by an idle cycle. Enabling Stay Awake during that cycle cancelled the cycle, but the screensaver window stayed open for about ten hours. The lock never ran, and the screensaver was still up when I came back to the machine.

Journal from omarchy-shell (times local, Oct 3):

12:30:23  idle-monitor: idle
12:30:23  idle-cycle-start: screensaver=150 lock=300
12:30:23  process-start: screensaver [[ ... ]] || omarchy-launch-screensaver
12:30:23  idle-monitor: active
12:30:23  idle-monitor-active: screensaver cycle remains armed
12:30:24  process-exit: screensaver exitCode=0 status=0
12:30:24  stay-awake: enabled ipc
12:30:24  idle-cycle-cancel: stay-awake
12:30:24  process-start: wake omarchy-system-wake
...
23:15:15  stay-awake: disabled ipc

No lock-system event occurs between 12:30 and 23:15.

Expected

Cancelling an idle cycle should close the screensaver window it launched, so the screensaver does not outlive the cycle.

Cause

cancelIdleCycle() in shell/plugins/services/idle/Service.qml stops the screensaver and lock timers and runs omarchy-system-wake. It does not close the org.omarchy.screensaver terminal. That terminal is started by hypr_exec in omarchy-launch-screensaver, so nothing in the cancel path owns it. omarchy-screensaver only exits on a keypress or a focus change, and enabling Stay Awake triggers neither.

This is from reading the source and the journal timeline above. I have not verified it with a debugger.

Steps to reproduce

  1. Set idle.screensaver to 150 and idle.lock to 300 in ~/.config/omarchy/shell.json.
  2. Go idle until the screensaver appears.
  3. Within the next 150 seconds, enable Stay Awake (omarchy toggle idle stay-awake, or the bar indicator).
  4. Wait well past 300 seconds. Expected: the screensaver is closed and nothing is locked. Observed: the screensaver window stays up and no lock runs.

Related

  • #12225: the screensaver self-exits and cancels the pending lock. Same cancelIdleCycle path, different trigger.
  • #12302: stay-awake turned off does not re-arm the idle monitor. Stay-awake state handling, opposite direction.

Neither covers a screensaver window that survives a stay-awake cancel.

System

  • Omarchy 4.0.4-1
  • Hyprland (Lua config), Quickshell omarchy-shell
  • Screensaver terminal: Ghostty (com.mitchellh.ghostty.desktop)
View raw text
## What happened

The screensaver was launched by an idle cycle. Enabling Stay Awake during that cycle cancelled the cycle, but the screensaver window stayed open for about ten hours. The lock never ran, and the screensaver was still up when I came back to the machine.

Journal from `omarchy-shell` (times local, Oct 3):

```
12:30:23  idle-monitor: idle
12:30:23  idle-cycle-start: screensaver=150 lock=300
12:30:23  process-start: screensaver [[ ... ]] || omarchy-launch-screensaver
12:30:23  idle-monitor: active
12:30:23  idle-monitor-active: screensaver cycle remains armed
12:30:24  process-exit: screensaver exitCode=0 status=0
12:30:24  stay-awake: enabled ipc
12:30:24  idle-cycle-cancel: stay-awake
12:30:24  process-start: wake omarchy-system-wake
...
23:15:15  stay-awake: disabled ipc
```

No `lock-system` event occurs between 12:30 and 23:15.

## Expected

Cancelling an idle cycle should close the screensaver window it launched, so the screensaver does not outlive the cycle.

## Cause

`cancelIdleCycle()` in `shell/plugins/services/idle/Service.qml` stops the screensaver and lock timers and runs `omarchy-system-wake`. It does not close the `org.omarchy.screensaver` terminal. That terminal is started by `hypr_exec` in `omarchy-launch-screensaver`, so nothing in the cancel path owns it. `omarchy-screensaver` only exits on a keypress or a focus change, and enabling Stay Awake triggers neither.

This is from reading the source and the journal timeline above. I have not verified it with a debugger.

## Steps to reproduce

1. Set `idle.screensaver` to 150 and `idle.lock` to 300 in `~/.config/omarchy/shell.json`.
2. Go idle until the screensaver appears.
3. Within the next 150 seconds, enable Stay Awake (`omarchy toggle idle stay-awake`, or the bar indicator).
4. Wait well past 300 seconds. Expected: the screensaver is closed and nothing is locked. Observed: the screensaver window stays up and no lock runs.

## Related

- #12225: the screensaver self-exits and cancels the pending lock. Same `cancelIdleCycle` path, different trigger.
- #12302: stay-awake turned off does not re-arm the idle monitor. Stay-awake state handling, opposite direction.

Neither covers a screensaver window that survives a stay-awake cancel.

## System

- Omarchy 4.0.4-1
- Hyprland (Lua config), Quickshell `omarchy-shell`
- Screensaver terminal: Ghostty (`com.mitchellh.ghostty.desktop`)

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

  • Related PRpr/11746· confirmed

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 02:26 UTC