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-voxtype-install: `voxtype setup gpu --enable || true` silently leaves dictation on CPU
Reported by dknoodle · filed Oct 2, 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 i9-11900K, NVIDIA RTX 4090 (nvidia-open-dkms 610.57.04), Omarchy 4.0.4, voxtype-bin 1.0.1
What's wrong?
omarchy-voxtype-install (same line on quattro, bin/omarchy-voxtype-install:19) does:
if omarchy-hw-vulkan; then
voxtype setup gpu --enable || true
fiOn this machine that step failed, and || true swallowed the failure. The installer finished with "Voxtype Dictation Ready", but voxtype was still on the CPU binary (voxtype-avx512). voxtype setup gpu --status showed the CPU backend, and nothing told the user.
Likely cause: voxtype setup gpu --enable switches backends by repointing the root-owned /usr/bin/voxtype symlink (to /usr/lib/voxtype/voxtype-vulkan), but the installer runs it as the normal user. Running sudo voxtype setup gpu --enable by hand fixed it.
Impact: dictation looks broken rather than slow. A 110 s clip took 109.6 s to transcribe on CPU (about 1× realtime), versus 0.99 s on Vulkan after the manual fix.
Steps:
1. On a Vulkan-capable machine, run Install Dictation (omarchy-voxtype-install).
2. Run voxtype setup gpu --status. It still reports the CPU backend.
Suggested fix: run the step with sudo (the script already declares omarchy:requires-sudo=true). If it still fails, tell the user instead of || true, e.g. a notification saying "GPU acceleration could not be enabled — run sudo voxtype setup gpu --enable".
View raw text
### System details Intel i9-11900K, NVIDIA RTX 4090 (nvidia-open-dkms 610.57.04), Omarchy 4.0.4, voxtype-bin 1.0.1 ### What's wrong? `omarchy-voxtype-install` (same line on `quattro`, `bin/omarchy-voxtype-install:19`) does: ```bash if omarchy-hw-vulkan; then voxtype setup gpu --enable || true fi ``` On this machine that step failed, and `|| true` swallowed the failure. The installer finished with "Voxtype Dictation Ready", but voxtype was still on the CPU binary (`voxtype-avx512`). `voxtype setup gpu --status` showed the CPU backend, and nothing told the user. Likely cause: `voxtype setup gpu --enable` switches backends by repointing the root-owned `/usr/bin/voxtype` symlink (to `/usr/lib/voxtype/voxtype-vulkan`), but the installer runs it as the normal user. Running `sudo voxtype setup gpu --enable` by hand fixed it. Impact: dictation looks broken rather than slow. A 110 s clip took 109.6 s to transcribe on CPU (about 1× realtime), versus 0.99 s on Vulkan after the manual fix. Steps: 1. On a Vulkan-capable machine, run Install Dictation (`omarchy-voxtype-install`). 2. Run `voxtype setup gpu --status`. It still reports the CPU backend. Suggested fix: run the step with `sudo` (the script already declares `omarchy:requires-sudo=true`). If it still fails, tell the user instead of `|| true`, e.g. a notification saying "GPU acceleration could not be enabled — run `sudo voxtype setup gpu --enable`".
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 20:50 UTC