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

windows-vm: two-minute readiness timeout reports normal first installation as failed

Reported by stoogs · filed Sep 2, 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

windows-vm: two-minute readiness timeout reports normal first installation as failedrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

  • CPU: 12th Gen Intel Core i7-1265U
  • GPU: Intel Alder Lake-UP3 GT2 (Iris Xe Graphics)
  • Omarchy: 4.0.2-1
  • Kernel: 7.1.9-arch1-2
  • Docker: 29.7.2
  • Docker Compose: 5.5.0
  • FreeRDP: 3.30.0
  • dockurr/windows: 6.05

What's wrong?

omarchy-windows-vm launch has a fixed two-minute readiness timeout. On a clean first start, that timeout includes downloading and preparing Windows installation media. A normal download can exceed two minutes, so the launcher reports:

Timeout: Windows VM did not report ready within 2 minutes

The desktop launcher then shows the generic notification Windows VM — Failed to start Windows VM, even though the container is healthy and continues its installation successfully in the background.

On this machine, the container started at 19:55:05Z, the download completed at 19:57:30Z, and Dockur reported Windows started successfully at 19:57:44Z—roughly 2 minutes 39 seconds after startup:

2026-09-02T19:55:05.533812391Z Starting Windows for Docker v6.05...
2026-09-02T19:55:09.783270535Z Downloading Windows 11...
2026-09-02T19:57:30.472148089Z 10% → ... → 100%
2026-09-02T19:57:44.229499065Z Windows started successfully...

The container remained running and the installation proceeded normally. This was reproduced from an empty ~/.windows directory after fixing the unrelated set-ID problem tracked in #9374.

Steps to reproduce

  1. Install/configure the Omarchy Windows VM.
  2. Ensure the VM storage is empty so Dockur must download Windows.
  3. Run omarchy-windows-vm launch and approve the Polkit prompt.
  4. Use a connection where downloading/preparing Windows takes more than two minutes.
  5. Observe the launcher report failure while docker ps still shows omarchy-windows running and docker logs shows continued progress.

Root cause

__priv_up_wait() polls every two seconds and fails after 60 iterations:

sleep 2
((++count > 60)) && {
  echo "Timeout: Windows VM did not report ready within 2 minutes" >&2
  return 1
}

This is much shorter than the documented first-install duration. The Windows VM manual says the initial download normally takes 10–15 minutes.

Expected behavior

The initial installation should not be reported as failed merely because downloading/preparing Windows takes longer than two minutes. Possible approaches:

  • Use a substantially longer first-install timeout when persistent VM media does not yet exist.
  • Treat a running container with active installation progress differently from a failed start.
  • Keep the short timeout for ordinary subsequent boots, while allowing the documented 10–15 minutes for initial provisioning.

The error shown by the desktop launcher should also distinguish a readiness timeout from authorization or container-start failure.

View raw text
### System details

- CPU: 12th Gen Intel Core i7-1265U
- GPU: Intel Alder Lake-UP3 GT2 (Iris Xe Graphics)
- Omarchy: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- Docker: 29.7.2
- Docker Compose: 5.5.0
- FreeRDP: 3.30.0
- dockurr/windows: 6.05

### What's wrong?

`omarchy-windows-vm launch` has a fixed two-minute readiness timeout. On a clean first start, that timeout includes downloading and preparing Windows installation media. A normal download can exceed two minutes, so the launcher reports:

```
Timeout: Windows VM did not report ready within 2 minutes
```

The desktop launcher then shows the generic notification `Windows VM — Failed to start Windows VM`, even though the container is healthy and continues its installation successfully in the background.

On this machine, the container started at `19:55:05Z`, the download completed at `19:57:30Z`, and Dockur reported Windows started successfully at `19:57:44Z`—roughly 2 minutes 39 seconds after startup:

```
2026-09-02T19:55:05.533812391Z Starting Windows for Docker v6.05...
2026-09-02T19:55:09.783270535Z Downloading Windows 11...
2026-09-02T19:57:30.472148089Z 10% → ... → 100%
2026-09-02T19:57:44.229499065Z Windows started successfully...
```

The container remained running and the installation proceeded normally. This was reproduced from an empty `~/.windows` directory after fixing the unrelated set-ID problem tracked in #9374.

### Steps to reproduce

1. Install/configure the Omarchy Windows VM.
2. Ensure the VM storage is empty so Dockur must download Windows.
3. Run `omarchy-windows-vm launch` and approve the Polkit prompt.
4. Use a connection where downloading/preparing Windows takes more than two minutes.
5. Observe the launcher report failure while `docker ps` still shows `omarchy-windows` running and `docker logs` shows continued progress.

### Root cause

`__priv_up_wait()` polls every two seconds and fails after 60 iterations:

```bash
sleep 2
((++count > 60)) && {
  echo "Timeout: Windows VM did not report ready within 2 minutes" >&2
  return 1
}
```

This is much shorter than the documented first-install duration. The Windows VM manual says the initial download normally takes 10–15 minutes.

### Expected behavior

The initial installation should not be reported as failed merely because downloading/preparing Windows takes longer than two minutes. Possible approaches:

- Use a substantially longer first-install timeout when persistent VM media does not yet exist.
- Treat a running container with active installation progress differently from a failed start.
- Keep the short timeout for ordinary subsequent boots, while allowing the documented 10–15 minutes for initial provisioning.

The error shown by the desktop launcher should also distinguish a readiness timeout from authorization or container-start failure.

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 10:38 UTC