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 does not detect package corruption after an interrupted pacman transaction
Reported by facusaldaa · filed Sep 11, 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
Omarchy 4.0.3-1
Problem
An unexpected interruption during the pacman portion of omarchy update
left visual-studio-code-bin only partially extracted.
After rebooting, running omarchy update again did not detect or repair the
inconsistent package. It completed its package step and subsequently offered
a reboot, while Visual Studio Code remained unusable.
Evidence
- The original pacman log records
transaction started, but no matching
transaction completed.
- Pacman reports visual-studio-code-bin 1.137.0-1 as installed.
- Its local database contains empty desc and files records.
- Installed package payloads are truncated:
- /usr/share/code/snapshot_blob.bin: 0 bytes; package archive: 346432 bytes
- /usr/share/code/v8_context_snapshot.bin: 0 bytes; package archive: 721176 bytes
- /usr/share/code/vk_swiftshader_icd.json: 0 bytes; package archive: 107 bytes
- Every Code launch aborts with:
FATAL:gin/v8_initializer.cc:689 Error mapping V8 startup snapshot file
- systemd-coredump recorded repeated SIGTRAP failures.
- There was no OOM event or storage exhaustion.
Expected behavior
When rerun after an interrupted package transaction, omarchy update should
detect an inconsistent pacman database or damaged installed package and stop
with repair instructions. It should not report completion or recommend rebooting
while the package database is inconsistent.
Notes
The evidence does not establish what caused the original interruption. The
reported Omarchy issue is specifically that subsequent update runs did not
detect the resulting inconsistent package state.
No core dump, username, hostname, network address, machine identifier, hardware
serial number, or home-directory path is included in this report.
Filed by GPT-5 via Codex.
View raw text
## System Omarchy 4.0.3-1 ## Problem An unexpected interruption during the pacman portion of `omarchy update` left `visual-studio-code-bin` only partially extracted. After rebooting, running `omarchy update` again did not detect or repair the inconsistent package. It completed its package step and subsequently offered a reboot, while Visual Studio Code remained unusable. ## Evidence - The original pacman log records `transaction started`, but no matching `transaction completed`. - Pacman reports `visual-studio-code-bin` 1.137.0-1 as installed. - Its local database contains empty `desc` and `files` records. - Installed package payloads are truncated: - `/usr/share/code/snapshot_blob.bin`: 0 bytes; package archive: 346432 bytes - `/usr/share/code/v8_context_snapshot.bin`: 0 bytes; package archive: 721176 bytes - `/usr/share/code/vk_swiftshader_icd.json`: 0 bytes; package archive: 107 bytes - Every Code launch aborts with: `FATAL:gin/v8_initializer.cc:689 Error mapping V8 startup snapshot file` - systemd-coredump recorded repeated SIGTRAP failures. - There was no OOM event or storage exhaustion. ## Expected behavior When rerun after an interrupted package transaction, `omarchy update` should detect an inconsistent pacman database or damaged installed package and stop with repair instructions. It should not report completion or recommend rebooting while the package database is inconsistent. ## Notes The evidence does not establish what caused the original interruption. The reported Omarchy issue is specifically that subsequent update runs did not detect the resulting inconsistent package state. No core dump, username, hostname, network address, machine identifier, hardware serial number, or home-directory path is included in this report. Filed by GPT-5 via Codex.
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
- Fixed bypr/11478· confirmed
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:50 UTC