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-26GitHub issuePublicFixed

Bar clock shows pre-suspend time for up to a minute after resume

Reported by zoan37 · filed Sep 28, 2026 · open at source

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

Bar clock shows pre-suspend time for up to a minute after resumerevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Dell XPS 13 (DX13260), Intel Wildcat Lake, Omarchy 4.0.4 (also checked against quattro HEAD), quickshell 0.3.1, systemd 261, s2idle

What's wrong?

After opening the lid, the bar clock shows the time from before suspend for up to 60 s, then jumps to the correct time. The delay differs on every wake.

Steps: close the lid a few minutes, open it, and watch the clock at the top.

Cause: the clock widget (shell/plugins/panels/clock/BarWidget.qml) uses Quickshell's SystemClock. That class waits for the next minute on a QTimer, and QTimer runs on CLOCK_MONOTONIC, which doesn't advance during suspend. So the time that was left in the minute at suspend still has to run out after wake. Upstream report: quickshell-mirror/quickshell#1212 (the source-level diagnosis is in the comments there).

Nothing in Omarchy refreshes the clock on wake. omarchy-system-sleep-monitor already listens for logind's PrepareForSleep, but it only acts on true (lock before sleep) and exits on the first event.

Possible fix until Quickshell fixes it: on PrepareForSleep(false), call the clock widget's existing IPC command omarchy.clock refresh. I tested that command and it corrects the clock immediately.

Workaround I'm running: a hook in /usr/lib/systemd/system-sleep/ that calls the clock's refresh on post. Verified on a real wake: the refresh lands ~270 ms after the lid opens. Script and gotchas (frozen user.slice during sleep hooks; qs ipc needs --pid from a hook with no Wayland display): https://github.com/zoan37/omarchy-setup/blob/master/bar-clock-stale-after-resume.md

View raw text
### System details

Dell XPS 13 (DX13260), Intel Wildcat Lake, Omarchy 4.0.4 (also checked against `quattro` HEAD), quickshell 0.3.1, systemd 261, s2idle

### What's wrong?

After opening the lid, the bar clock shows the time from before suspend for up to 60 s, then jumps to the correct time. The delay differs on every wake.

**Steps:** close the lid a few minutes, open it, and watch the clock at the top.

**Cause:** the clock widget (`shell/plugins/panels/clock/BarWidget.qml`) uses Quickshell's `SystemClock`. That class waits for the next minute on a `QTimer`, and `QTimer` runs on `CLOCK_MONOTONIC`, which doesn't advance during suspend. So the time that was left in the minute at suspend still has to run out after wake. Upstream report: quickshell-mirror/quickshell#1212 (the source-level diagnosis is in the comments there).

Nothing in Omarchy refreshes the clock on wake. `omarchy-system-sleep-monitor` already listens for logind's `PrepareForSleep`, but it only acts on `true` (lock before sleep) and exits on the first event.

**Possible fix until Quickshell fixes it:** on `PrepareForSleep(false)`, call the clock widget's existing IPC command `omarchy.clock refresh`. I tested that command and it corrects the clock immediately.

**Workaround I'm running:** a hook in `/usr/lib/systemd/system-sleep/` that calls the clock's refresh on `post`. Verified on a real wake: the refresh lands ~270 ms after the lid opens. Script and gotchas (frozen `user.slice` during sleep hooks; `qs ipc` needs `--pid` from a hook with no Wayland display): https://github.com/zoan37/omarchy-setup/blob/master/bar-clock-stale-after-resume.md

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

  • Fixed bypr/12277· confirmed
  • Fixed bypr/14264· confirmed
  • Fixed bypr/10138· confirmed
  • Fixed bypr/13541· confirmed
  • Fixed bypr/13347· confirmed
  • Fixed bypr/13804· 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 19:54 UTC