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.
Voxtype does not symlink to voxtype-vulkan on Vulkan enabled system
Reported by sgruendel · filed Aug 16, 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
AMD Radeon 780M Graphics, Omarchy Quattro
What's wrong?
When installing voxtype on a Vulkan enabled system, output shows
Error: Failed to remove existing /usr/bin/voxtype (need sudo?): Permission denied (os error 13)Kimi K3 Root cause: voxtype setup gpu --enable rewrites the root-owned /usr/bin/voxtype symlink, but omarchy-voxtype-install ran it as your user — hence "Permission denied (os error 13)" on line 93 of the log. The trailing || true then hid the failure, so the install "succeeded" while /usr/bin/voxtype kept pointing at voxtype-avx512 instead of voxtype-vulkan. The "# omarchy:requires-sudo=true" metadata doesn't run the script as root (nor should it — the rest writes to $HOME); it's just router metadata.
View raw text
### System details AMD Radeon 780M Graphics, Omarchy Quattro ### What's wrong? When installing voxtype on a Vulkan enabled system, output shows ``` Error: Failed to remove existing /usr/bin/voxtype (need sudo?): Permission denied (os error 13) ``` Kimi K3 Root cause: `voxtype setup gpu --enable` rewrites the root-owned `/usr/bin/voxtype` symlink, but `omarchy-voxtype-install` ran it as your user — hence "Permission denied (os error 13)" on line 93 of the log. The trailing `|| true` then hid the failure, so the install "succeeded" while `/usr/bin/voxtype` kept pointing at `voxtype-avx512` instead of `voxtype-vulkan`. The "# omarchy:requires-sudo=true" metadata doesn't run the script as root (nor should it — the rest writes to $HOME); it's just router metadata.
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 04:19 UTC