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-61GitHub issuePublicDecided· Out of scope

Dual boot with Windows: a clock in local time keeps new snapshots out of the Limine menu for hours

Reported by peregrinus879 · filed Sep 26, 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

Dual boot with Windows: a clock in local time keeps new snapshots out of the Limine menu for hoursrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

ASUS Vivobook TP3402VA (Intel), Omarchy 4.0.4, limine-snapper-sync 1.31.0, Windows 11 Home installed beside it

What's wrong?

On a dual-boot machine Windows keeps the hardware clock in local time and Linux reads it as UTC, so after a Windows session Omarchy starts with the system clock ahead by the UTC offset (four hours here) until NTP corrects it. A snapshot taken in that window, such as the one omarchy-update takes before it updates, carries a time in the future. limine-snapper-sync then adds no menu entry for any later snapshot until real time has passed that stamp, because its sync treats the newest snapshot as new only when its time is later than the last one it recorded. Nothing says so: snapper list shows the snapshots, the journal shows Saved: snapshots.json and Updated: limine.conf, and the menu lacks their entries.

I've reported the limine-snapper-sync side: https://gitlab.com/Zesko/limine-snapper-sync/-/work_items/17. On Omarchy's side, either of these would close it for dual-boot users:

  1. Settle the clock convention once: timedatectl set-local-rtc 1 where the installer found Windows, or tell Windows to keep UTC (the RealTimeIsUniversal registry value) in the dual-boot manual page.
  2. Have omarchy-update wait, for a bounded time, until timedatectl show -p NTPSynchronized --value reads yes before it takes its snapshot.

To reproduce: set the clock four hours ahead, take a snapshot, set it right, take another; the second gets no menu entry until four hours have passed.

Co-Authored-By: Claude Opus 5.5

View raw text
### System details

ASUS Vivobook TP3402VA (Intel), Omarchy 4.0.4, limine-snapper-sync 1.31.0, Windows 11 Home installed beside it

### What's wrong?

On a dual-boot machine Windows keeps the hardware clock in local time and Linux reads it as UTC, so after a Windows session Omarchy starts with the system clock ahead by the UTC offset (four hours here) until NTP corrects it. A snapshot taken in that window, such as the one `omarchy-update` takes before it updates, carries a time in the future. limine-snapper-sync then adds no menu entry for any later snapshot until real time has passed that stamp, because its sync treats the newest snapshot as new only when its time is later than the last one it recorded. Nothing says so: `snapper list` shows the snapshots, the journal shows `Saved: snapshots.json` and `Updated: limine.conf`, and the menu lacks their entries.

I've reported the limine-snapper-sync side: https://gitlab.com/Zesko/limine-snapper-sync/-/work_items/17. On Omarchy's side, either of these would close it for dual-boot users:

1. Settle the clock convention once: `timedatectl set-local-rtc 1` where the installer found Windows, or tell Windows to keep UTC (the `RealTimeIsUniversal` registry value) in the dual-boot manual page.
2. Have `omarchy-update` wait, for a bounded time, until `timedatectl show -p NTPSynchronized --value` reads `yes` before it takes its snapshot.

To reproduce: set the clock four hours ahead, take a snapshot, set it right, take another; the second gets no menu entry until four hours have passed.

Co-Authored-By: Claude Opus 5.5

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 18:55 UTC