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

Screensaver resets hypridle timer

Reported by pomartel · filed Dec 17, 2025Closed upstream on 2026-01-03 by its own reporter pomartel. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

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

Screensaver resets hypridle timerrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Lenovo X1 Carbon Gen 13, Omarchy 3.2.3

What's wrong?

Steps to reproduce

Replace you ~/.config/hypr/hypridle.confconfig with this one:

general {
    lock_cmd = omarchy-lock-screen                # lock screen and 1password
    before_sleep_cmd = loginctl lock-session      # lock before suspend.
    after_sleep_cmd = hyprctl dispatch dpms on    # to avoid having to press a key twice to turn on the display.
    inhibit_sleep = 3                             # wait until screen is locked
}

listener {
    timeout = 10
    on-timeout = pidof hyprlock || omarchy-launch-screensaver
 }

listener {
    timeout = 15
    on-timeout = hyprctl dispatch dpms off # screen off when timeout has passed
    on-resume = hyprctl dispatch dpms on && brightnessctl -r # screen on when activity is detected
}

Restart hypridle : 

omarchy-restart-hypridle

Expected behaviour

The screensaver should kick in after 10 seconds. The screen should turn off 5 seconds later.

Actual behaviour

The screensaver kicks in after 10 seconds but it takes another 15 seconds for the screen to turn off. It appears the screensaver resets the idle timer.

View raw text
### System details

Lenovo X1 Carbon Gen 13, Omarchy 3.2.3

### What's wrong?

## Steps to reproduce

Replace you `~/.config/hypr/hypridle.conf`config with this one:

```ìni
general {
    lock_cmd = omarchy-lock-screen                # lock screen and 1password
    before_sleep_cmd = loginctl lock-session      # lock before suspend.
    after_sleep_cmd = hyprctl dispatch dpms on    # to avoid having to press a key twice to turn on the display.
    inhibit_sleep = 3                             # wait until screen is locked
}

listener {
    timeout = 10
    on-timeout = pidof hyprlock || omarchy-launch-screensaver
 }

listener {
    timeout = 15
    on-timeout = hyprctl dispatch dpms off # screen off when timeout has passed
    on-resume = hyprctl dispatch dpms on && brightnessctl -r # screen on when activity is detected
}
````

Restart hypridle : 
```
omarchy-restart-hypridle
```

## Expected behaviour

The screensaver should kick in after 10 seconds. The screen should turn off 5 seconds later.

## Actual behaviour

The screensaver kicks in after 10 seconds but it takes another 15 seconds for the screen to turn off. It appears the screensaver resets the idle timer.

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.