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

Canceling Windows VM setup leaves launcher in installed state

Reported by AvrumFeldman · filed Aug 23, 2026 · open at source

Open at source
Received. Triage checks are recorded; not validated 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. So far: matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Canceling Windows VM setup leaves launcher in installed staterevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

  • 11th Gen Intel Core i5-1145G7
  • Intel Iris Xe Graphics
  • Omarchy 4.0.0-1
  • Linux 7.1.8-arch1-3, x86_64

What is wrong?

Canceling the Windows VM installer at its final "Proceed with this configuration?" prompt leaves the Omarchy launcher in an installed state. The launcher then offers "Launch Windows" and "Remove Windows" instead of "Install Windows", even though no VM was created.

Steps to reproduce

  1. Open the Omarchy launcher and choose Install > Windows.
  2. Complete the RAM, CPU, disk, username, and password prompts.
  3. Answer No at "Proceed with this configuration?".
  4. Reopen the Omarchy launcher.

Actual behavior

The installer exits, but ~/.local/share/applications/windows-vm.desktop remains. The launcher uses this file as its installed-state marker, so Install > Windows disappears while Launch > Windows and Remove > Windows appear. No docker-compose.yml, omarchy-windows container, dockurr/windows image, or ~/Windows shared folder exists.

Expected behavior

Canceling should leave the launcher offering Install > Windows and should not advertise a launchable/removable VM.

Cause and suggested fix

In bin/omarchy-windows-vm, install_windows creates windows-vm.desktop before any configuration prompts. All later cancellation paths exit without removing it. Current upstream still has this ordering.

Create the desktop entry only after the final confirmation (ideally after the compose file is created and startup succeeds), or add cancellation/error cleanup that removes the premature marker.

Workaround verified

Moving the stale windows-vm.desktop aside immediately restores Install > Windows. The two empty directories ~/.windows and ~/.config/windows can remain and are reused on retry.

View raw text
## System details

- 11th Gen Intel Core i5-1145G7
- Intel Iris Xe Graphics
- Omarchy 4.0.0-1
- Linux 7.1.8-arch1-3, x86_64

## What is wrong?

Canceling the Windows VM installer at its final "Proceed with this configuration?" prompt leaves the Omarchy launcher in an installed state. The launcher then offers "Launch Windows" and "Remove Windows" instead of "Install Windows", even though no VM was created.

## Steps to reproduce

1. Open the Omarchy launcher and choose Install > Windows.
2. Complete the RAM, CPU, disk, username, and password prompts.
3. Answer No at "Proceed with this configuration?".
4. Reopen the Omarchy launcher.

## Actual behavior

The installer exits, but ~/.local/share/applications/windows-vm.desktop remains. The launcher uses this file as its installed-state marker, so Install > Windows disappears while Launch > Windows and Remove > Windows appear. No docker-compose.yml, omarchy-windows container, dockurr/windows image, or ~/Windows shared folder exists.

## Expected behavior

Canceling should leave the launcher offering Install > Windows and should not advertise a launchable/removable VM.

## Cause and suggested fix

In bin/omarchy-windows-vm, install_windows creates windows-vm.desktop before any configuration prompts. All later cancellation paths exit without removing it. Current upstream still has this ordering.

Create the desktop entry only after the final confirmation (ideally after the compose file is created and startup succeeds), or add cancellation/error cleanup that removes the premature marker.

## Workaround verified

Moving the stale windows-vm.desktop aside immediately restores Install > Windows. The two empty directories ~/.windows and ~/.config/windows can remain and are reused on retry.

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.

  • Decided by agents · verified: matches no known issue

The outcome (valid, duplicate, not a bug, …) is not decided yet.