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.
Consider enabling btrfs qgroups so snapper's space-aware cleanup works
Reported by brightmeows · filed Oct 6, 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
Current behavior
Omarchy configures snapper with NUMBER_CLEANUP=yes (count-based, capped at 5). Without qgroups, snapper has no notion of snapshot space: count-based cleanup still deletes when the disk is full, but nothing warns before the filesystem runs out, and snapper list --space-used reports nothing.
Suggestion
btrfs quota enable / + btrfs quota rescan / at install (or a migration). One-time rescan cost (minutes on a 350 GiB root); steady-state qgroup overhead is small at this subvolume count (7 subvolumes + 5 snapshots).
Tested on 4.0.4: after enabling, per-subvolume accounting comes up cleanly and snapper's SPACE_LIMIT/FREE_LIMIT defaults become effective.
Question
More an "any appetite for this" than a demand — snapshot policy here is deliberately minimal (timeline disabled, pacman pre-transaction snapshots only). If keeping defaults lean is the call, feel free to close; I mostly wanted the consideration on record.
View raw text
## Current behavior Omarchy configures snapper with `NUMBER_CLEANUP=yes` (count-based, capped at 5). Without qgroups, snapper has no notion of snapshot space: count-based cleanup still deletes when the disk is full, but nothing warns before the filesystem runs out, and `snapper list --space-used` reports nothing. ## Suggestion `btrfs quota enable /` + `btrfs quota rescan /` at install (or a migration). One-time rescan cost (minutes on a 350 GiB root); steady-state qgroup overhead is small at this subvolume count (7 subvolumes + 5 snapshots). Tested on 4.0.4: after enabling, per-subvolume accounting comes up cleanly and snapper's `SPACE_LIMIT`/`FREE_LIMIT` defaults become effective. ## Question More an "any appetite for this" than a demand — snapshot policy here is deliberately minimal (timeline disabled, pacman pre-transaction snapshots only). If keeping defaults lean is the call, feel free to close; I mostly wanted the consideration on record.
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 21:55 UTC