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

Windows VM startup fails silently when shared directory has setgid

Reported by bokology · filed Sep 5, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #9334 (R-1173). GitHub close reason: completed.

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

Windows VM startup fails silently when shared directory has setgidrevision 1 · captured 2026-10-04 12:10 UTC via poll

Windows VM startup fails silently when shared directory has setgid

Destination: https://github.com/basecamp/omarchy/issues

System details

Omarchy 4.0.2-1; GNU coreutils 9.11-2; kernel 7.1.9-arch1-2; Intel Core i7-1360P; Intel Iris Xe Graphics; Hyprland 0.56.2.

Failure

An installed Windows VM fails to launch when ~/Windows has mode 2700 (setgid). Authorization succeeds, but the launcher displays “Failed to start Windows VM!” and exits before Docker startup. Directly invoking the installed privileged startup helper reproduced exit status 1 without an explanatory error.

In prepare_caller_mounts() in bin/omarchy-windows-vm, chmod 0700 is applied to the pinned source directories. Their modes are then read with stat -Lc '%a' and required to be exactly 700. GNU chmod preserves directory setgid with chmod 0700, so 2700 remains 2700 and fails this check. The same logic was verified in the current upstream file.

Reproduction

On an existing installation using the stock launcher:

  1. Run chmod 2700 "$HOME/Windows".
  2. Run /usr/bin/omarchy-windows-vm launch and authorize the prompt.
  3. Observe startup failure.
  4. Run chmod g-s "$HOME/Windows" and retry. Startup succeeds.

Minimal reproduction without modifying VM data:

probe_dir=$(mktemp -d)
chmod 2700 "$probe_dir"
chmod 0700 "$probe_dir"
stat -c '%a' "$probe_dir"  # Prints 2700, but the helper requires 700
rmdir "$probe_dir"

Validation

The affected machine had mode 700 on ~/.windows and 2700 on ~/Windows. Clearing only setgid allowed the container to start and the helper's Windows-ready check to complete with exit status 0. RDP subsequently connected successfully.

The flag was observed back at 2700 on a later launch, reproducing the failure. Clearing it again restored connection. The process restoring the flag has not been identified; this report does not attribute it to Docker or Samba.

Expected behavior and possible fix

Explicitly clear special permission bits on the already-pinned directories before enforcing exact mode 700, retaining the existing ownership, path, and mount safety checks. GNU chmod 00700 is a candidate; the privileged procfd path should have a regression test. Report the rejected mode instead of exiting silently.

The local workaround is a personal launcher that clears setgid before invoking the packaged helper. No packaged files were modified.

Diagnostics

omarchy-debug --no-sudo --print was collected locally. Relevant system details are summarized above. Full logs, credentials, personal usernames, and device identifiers are omitted. Command output and the minimal reproduction document this preflight failure without interrupting the now-running VM for a screenshot.

View raw text
# Windows VM startup fails silently when shared directory has setgid

Destination: https://github.com/basecamp/omarchy/issues

## System details

Omarchy 4.0.2-1; GNU coreutils 9.11-2; kernel 7.1.9-arch1-2; Intel Core i7-1360P; Intel Iris Xe Graphics; Hyprland 0.56.2.

## Failure

An installed Windows VM fails to launch when `~/Windows` has mode `2700` (setgid). Authorization succeeds, but the launcher displays “Failed to start Windows VM!” and exits before Docker startup. Directly invoking the installed privileged startup helper reproduced exit status 1 without an explanatory error.

In `prepare_caller_mounts()` in `bin/omarchy-windows-vm`, `chmod 0700` is applied to the pinned source directories. Their modes are then read with `stat -Lc '%a'` and required to be exactly `700`. GNU chmod preserves directory setgid with `chmod 0700`, so `2700` remains `2700` and fails this check. The same logic was verified in the current upstream file.

## Reproduction

On an existing installation using the stock launcher:

1. Run `chmod 2700 "$HOME/Windows"`.
2. Run `/usr/bin/omarchy-windows-vm launch` and authorize the prompt.
3. Observe startup failure.
4. Run `chmod g-s "$HOME/Windows"` and retry. Startup succeeds.

Minimal reproduction without modifying VM data:

```bash
probe_dir=$(mktemp -d)
chmod 2700 "$probe_dir"
chmod 0700 "$probe_dir"
stat -c '%a' "$probe_dir"  # Prints 2700, but the helper requires 700
rmdir "$probe_dir"
```

## Validation

The affected machine had mode `700` on `~/.windows` and `2700` on `~/Windows`. Clearing only setgid allowed the container to start and the helper's Windows-ready check to complete with exit status 0. RDP subsequently connected successfully.

The flag was observed back at `2700` on a later launch, reproducing the failure. Clearing it again restored connection. The process restoring the flag has not been identified; this report does not attribute it to Docker or Samba.

## Expected behavior and possible fix

Explicitly clear special permission bits on the already-pinned directories before enforcing exact mode `700`, retaining the existing ownership, path, and mount safety checks. GNU `chmod 00700` is a candidate; the privileged procfd path should have a regression test. Report the rejected mode instead of exiting silently.

The local workaround is a personal launcher that clears setgid before invoking the packaged helper. No packaged files were modified.

## Diagnostics

`omarchy-debug --no-sudo --print` was collected locally. Relevant system details are summarized above. Full logs, credentials, personal usernames, and device identifiers are omitted. Command output and the minimal reproduction document this preflight failure without interrupting the now-running VM for a screenshot.

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.