Proof Portal

Sign in
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-5231GitHub issuePublicDecided· Out of scope

Dismissing the screensaver exits every other graphical application

Reported by rgrz · filed Oct 8, 2026 · 2 revisionsClosed upstream on 2026-10-10 by its own reporter rgrz. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Open at source
Decided: Out of scope — decided by agents · verified 2 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

Revision12 (current)
Dismissing the screensaver exits every other graphical applicationrevision 2 · captured 2026-10-08 07:14 UTC via poll

System details

AMD Ryzen 7 5800X, NVIDIA GeForce RTX 3060 (nvidia-open 610.57.04), Dell U2515H on HDMI-A-1 at 2560x1440. Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland 0.56.2.

What's wrong?

Dismissing the screensaver exits every other graphical application. Hyprland and the shell stay running. There is no core dump and no OOM kill.

~/.config/omarchy/shell.json has idle.screensaver 150 and idle.lock 300. This happened on the screensaver, before the lock.

Times are CEST on 2026-10-08:

  • 08:44:04 the idle cycle starts and launches the screensaver.
  • 08:45:29 the screensaver window closes. omarchy-shell logs idle-cycle-cancel: screensaver-dismissed and runs omarchy-system-wake.
  • In that same second these scopes exit:
  • Chrome, running since boot on Oct 6 at 21:09
  • Cursor, up 8h 33m. Its own log says the extension hosts exited with code 0 at 08:45:29.552
  • T3 Code, Grok, and a terminal, each up about 16h
  • The Hyprland process is still the one from boot (Oct 6 21:07). hyprland.log shows HDMI-A-1 disabled and modeset back to 2560x1440 twice, in the same stretch as the mouse clicks that dismissed the screensaver.

omarchy-system-wake calls omarchy-brightness-display on, which dispatches a DPMS enable. That command already notes that a DPMS enable forces a modeset.

Two nearby events did not close the applications:

  • The overnight lock blanked this same HDMI output. The applications were still there at unlock (08:33).
  • omarchy update at 08:34 upgraded aether, cursor-bin, google-chrome, and mise, then restarted the shell. The applications survived that and died 11 minutes later, on the screensaver wake.

Expected: dismissing the screensaver closes only the screensaver terminal and wakes the display.

Debug log, expires in 24h: https://logs.omarchy.org/F4Il8q

Firewall lines and the local username were removed from this copy. The idle lines are user-journal DEBUG and are not in that warning-level log. The timeline above is from journalctl --user.

View raw text
### System details

AMD Ryzen 7 5800X, NVIDIA GeForce RTX 3060 (nvidia-open 610.57.04), Dell U2515H on HDMI-A-1 at 2560x1440. Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, Hyprland 0.56.2.

### What's wrong?

Dismissing the screensaver exits every other graphical application. Hyprland and the shell stay running. There is no core dump and no OOM kill.

`~/.config/omarchy/shell.json` has `idle.screensaver` 150 and `idle.lock` 300. This happened on the screensaver, before the lock.

Times are CEST on 2026-10-08:

- 08:44:04 the idle cycle starts and launches the screensaver.
- 08:45:29 the screensaver window closes. `omarchy-shell` logs `idle-cycle-cancel: screensaver-dismissed` and runs `omarchy-system-wake`.
- In that same second these scopes exit:
  - Chrome, running since boot on Oct 6 at 21:09
  - Cursor, up 8h 33m. Its own log says the extension hosts exited with code 0 at 08:45:29.552
  - T3 Code, Grok, and a terminal, each up about 16h
- The Hyprland process is still the one from boot (Oct 6 21:07). `hyprland.log` shows HDMI-A-1 disabled and modeset back to 2560x1440 twice, in the same stretch as the mouse clicks that dismissed the screensaver.

`omarchy-system-wake` calls `omarchy-brightness-display on`, which dispatches a DPMS enable. That command already notes that a DPMS enable forces a modeset.

Two nearby events did not close the applications:

- The overnight lock blanked this same HDMI output. The applications were still there at unlock (08:33).
- `omarchy update` at 08:34 upgraded aether, cursor-bin, google-chrome, and mise, then restarted the shell. The applications survived that and died 11 minutes later, on the screensaver wake.

Expected: dismissing the screensaver closes only the screensaver terminal and wakes the display.

Debug log, expires in 24h: https://logs.omarchy.org/F4Il8q

Firewall lines and the local username were removed from this copy. The idle lines are user-journal DEBUG and are not in that warning-level log. The timeline above is from `journalctl --user`.

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/11626· 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 22:47 UTC