Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
omarchy update fails at snapshot step when a swapfile is active on the btrfs root subvolume
Reported by markbus-ai · filed Jul 31, 2026 · open at source
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
System details
Intel Celeron N5100 (Jasper Lake, 4 cores), 3.6 GiB RAM, Intel UHD Graphics, Omarchy 4.0.0.r1367.g2fb65d0-1, kernel 7.1.4-arch1-1, btrfs root on LUKS (single @ subvolume).
What's wrong?
omarchy update fails at the "Create system snapshot" step with Error al crear la imagen. (snapper's localized "Error creating the image."). The update aborts before any packages are touched.
Root cause: the btrfs root subvolume contains an active swapfile (/swapfile, 4 GiB, enabled via /etc/fstab), and the kernel refuses to snapshot a subvolume containing an active swapfile:
kernel: BTRFS warning (device dm-0): cannot snapshot subvolume with active swapfileomarchy-snapshot runs snapper -c root create, which fails; the journal shows the snapshot subvolume being created and immediately deleted again:
limine-snapper-watcher[977]: [EVENT] CREATE,ISDIR -> 37
limine-snapper-watcher[977]: [EVENT] DELETE,ISDIR -> 37Steps to reproduce:
1. Have an active swapfile inside the btrfs root subvolume: truncate -s 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile (plus an /etc/fstab entry, sw option)
2. Run omarchy update and confirm
3. Update aborts at the "Create system snapshot" step with Error al crear la imagen.
Expected behavior: the snapshot step should not break the update when a swapfile is present — for example, temporarily swapoff/swapon around snapshot creation (safe while another swap device is available), or skip the snapshot with a clear warning, or at least document the limitation.
Actual behavior: the update aborts with no explanation beyond the localized snapper error; the user must discover the workaround manually.
Workaround: sudo swapoff /swapfile before omarchy update, then sudo swapon /swapfile afterwards.
Note: not related to #5811 (that one is about limine-snapper-sync / ROOT_SNAPSHOTS_PATH).
View raw text
### System details Intel Celeron N5100 (Jasper Lake, 4 cores), 3.6 GiB RAM, Intel UHD Graphics, Omarchy 4.0.0.r1367.g2fb65d0-1, kernel 7.1.4-arch1-1, btrfs root on LUKS (single `@` subvolume). ### What's wrong? `omarchy update` fails at the "Create system snapshot" step with `Error al crear la imagen.` (snapper's localized "Error creating the image."). The update aborts before any packages are touched. Root cause: the btrfs root subvolume contains an **active swapfile** (`/swapfile`, 4 GiB, enabled via `/etc/fstab`), and the kernel refuses to snapshot a subvolume containing an active swapfile: ``` kernel: BTRFS warning (device dm-0): cannot snapshot subvolume with active swapfile ``` `omarchy-snapshot` runs `snapper -c root create`, which fails; the journal shows the snapshot subvolume being created and immediately deleted again: ``` limine-snapper-watcher[977]: [EVENT] CREATE,ISDIR -> 37 limine-snapper-watcher[977]: [EVENT] DELETE,ISDIR -> 37 ``` Steps to reproduce: 1. Have an active swapfile inside the btrfs root subvolume: `truncate -s 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile` (plus an `/etc/fstab` entry, `sw` option) 2. Run `omarchy update` and confirm 3. Update aborts at the "Create system snapshot" step with `Error al crear la imagen.` Expected behavior: the snapshot step should not break the update when a swapfile is present — for example, temporarily `swapoff`/`swapon` around snapshot creation (safe while another swap device is available), or skip the snapshot with a clear warning, or at least document the limitation. Actual behavior: the update aborts with no explanation beyond the localized snapper error; the user must discover the workaround manually. Workaround: `sudo swapoff /swapfile` before `omarchy update`, then `sudo swapon /swapfile` afterwards. Note: not related to #5811 (that one is about limine-snapper-sync / `ROOT_SNAPSHOTS_PATH`).
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 03:58 UTC