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-3001GitHub issuePublicReceived

Unlocking the Screen Doesn't Terminate the Screensaver

Reported by Chase78712002 · filed Sep 24, 2025Closed upstream on 2025-10-24 by its own reporter Chase78712002, as a duplicate of #1910 (R-3001). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Unlocking the Screen Doesn't Terminate the Screensaverrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

AMD Ryzen 5 2600, NVIDIA GeForce GTX 1070, Omarchy v3.0.1

What's wrong?

By default, the screensaver activates after 2.5 minutes of inactivity. The lock screen appears 2.5 minutes later

Problem:
Unlocking the screen doesn't terminate the screensaver, so a key press is still required. This also causes the mouse cursor to remain hidden while the screen is locked. As a result, users cannot access the cursor, which can be inconvenient if the lock screen includes clickable buttons such as suspend or restart.

Proposed Fix:
Terminate the screensaver just before the screen locks.

<img width="799" height="442" alt="Image" src="https://github.com/user-attachments/assets/be5a68a0-6cf8-4c92-9752-92482ff1a592" />

View raw text
### System details

AMD Ryzen 5 2600, NVIDIA GeForce GTX 1070, Omarchy v3.0.1

### What's wrong?

By default, the screensaver activates after 2.5 minutes of inactivity.  The lock screen appears 2.5 minutes later

**Problem:** 
Unlocking the screen doesn't terminate the screensaver, so a key press is still required. This also causes the mouse cursor to remain hidden while the screen is locked. As a result, users cannot access the cursor, which can be inconvenient if the lock screen includes clickable buttons such as `suspend` or `restart`.

**Proposed Fix:**
Terminate the screensaver just before the screen locks.

<img width="799" height="442" alt="Image" src="https://github.com/user-attachments/assets/be5a68a0-6cf8-4c92-9752-92482ff1a592" />
  • be5a68a0-6cf8-4c92-9752-92482ff1a592

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.