Proof Portal

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

omarchy-snapshot: handle non-subvolume /.snapshots with clear diagnostic and recovery instructions

Reported by patsonatorEFPL · filed Sep 10, 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

omarchy-snapshot: handle non-subvolume /.snapshots with clear diagnostic and recovery instructionsrevision 1 · captured 2026-09-28 21:23 UTC via poll

Summary

When a system is restored from backups (rsync, tar, clone), /.snapshots often ends up as a plain directory instead of a Btrfs subvolume. When omarchy update or omarchy-snapshot create runs, snapper throws an opaque error:

Create system snapshot
IO Error (.snapshots is not a btrfs subvolume).
Continuing the update without a snapshot.

Subsequently, snapper-cleanup.timer and limine-snapper-sync.service repeatedly fail in the background without actionable feedback for the user.

Root Cause

/usr/share/omarchy/bin/omarchy-snapshot delegates directly to snapper create without validating whether /.snapshots is actually a Btrfs subvolume. If /.snapshots exists as a standard POSIX directory, Snapper aborts with IO Error (.snapshots is not a btrfs subvolume).

Proposed Fix

In omarchy-snapshot (under create), perform a pre-check:

if [[ -d "/.snapshots" ]] && ! btrfs subvolume show "/.snapshots" &>/dev/null; then
  echo -e "\e[31mError: /.snapshots exists but is not a valid Btrfs subvolume.\e[0m" >&2
  echo "Fix with: sudo rm -rf /.snapshots && sudo btrfs subvolume create /.snapshots && sudo chmod 750 /.snapshots" >&2
  exit 1
fi

System Info

Omarchy version: 4.0.3-1
Filesystem: Btrfs on Linux 7.1.9-arch1-2

Filed by gemini-3.8-flash-high via opencode.

View raw text

### Summary
When a system is restored from backups (rsync, tar, clone), `/.snapshots` often ends up as a plain directory instead of a Btrfs subvolume. When `omarchy update` or `omarchy-snapshot create` runs, snapper throws an opaque error:
```text
Create system snapshot
IO Error (.snapshots is not a btrfs subvolume).
Continuing the update without a snapshot.
```
Subsequently, `snapper-cleanup.timer` and `limine-snapper-sync.service` repeatedly fail in the background without actionable feedback for the user.

### Root Cause
`/usr/share/omarchy/bin/omarchy-snapshot` delegates directly to `snapper create` without validating whether `/.snapshots` is actually a Btrfs subvolume. If `/.snapshots` exists as a standard POSIX directory, Snapper aborts with `IO Error (.snapshots is not a btrfs subvolume)`.

### Proposed Fix
In `omarchy-snapshot` (under `create`), perform a pre-check:
```bash
if [[ -d "/.snapshots" ]] && ! btrfs subvolume show "/.snapshots" &>/dev/null; then
  echo -e "\e[31mError: /.snapshots exists but is not a valid Btrfs subvolume.\e[0m" >&2
  echo "Fix with: sudo rm -rf /.snapshots && sudo btrfs subvolume create /.snapshots && sudo chmod 750 /.snapshots" >&2
  exit 1
fi
```

### System Info
- Omarchy version: 4.0.3-1
- Filesystem: Btrfs on Linux 7.1.9-arch1-2

> Filed by gemini-3.8-flash-high via opencode.

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 11:23 UTC

Proof

History & reports

Reference