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.
Dictation installer offers x86-only voxtype-bin on Apple Silicon, making Voxtype uninstallable
Reported by twitchax · filed Aug 27, 2026 · open at source
This defect is tracked under R-623. This report describes the same defect, so it is folded under it in the inbox.
Earliest report of this defect: R-1384 (filed Aug 27, 2026).
Decided by agents · verified· Oct 9, 2026
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?
- 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
- Omarchy: 4.0.0.r6673.g5939caf-1
- Hardware: Apple MacBook Air (M1, 2020) —
apple,j313/apple,t8103 - CPU: Apple M1 (aarch64)
- Kernel: 7.1.6-1-1-ARCH (
linux-asahi7.1.6.asahi1-1) - Package:
voxtype-bin0.7.5-1 omarchy-hw-apple-silicon→ true
What's wrong?
bin/omarchy-voxtype-install installs the prebuilt package unconditionally:
omarchy-pkg-add wtype voxtype-binvoxtype-bin declares arch=('x86_64'), so on Apple Silicon it cannot be built
or installed at all:
==> ERROR: voxtype-bin is not available for the 'aarch64' architecture.Dictation is therefore unreachable on every Apple Silicon Omarchy install.voxtype never lands on PATH, so the guard indefault/hypr/bindings/voxtype.lua never fires:
if o.cmd_present("voxtype") then
o.bind("SUPER + CTRL + X", "Toggle dictation", "voxtype record toggle")
o.bind("F9", "Start dictation (push-to-talk)", "voxtype record start")
...
endF9 and SUPER + CTRL + X silently do nothing, and the Dictation bar indicator
stays inert.
Users are actively steered into this dead end:install/user/first-run/install-voxtype.hook raises a critical notification
inviting them to "Install voice dictation for Omarchy", whose --exec runs the
installer that cannot succeed on this hardware.
Expected
Either dictation installs successfully on aarch64, or Omarchy declines to offer
it rather than prompting for an install that always fails.
Steps to reproduce
- Omarchy on Apple Silicon (Asahi, aarch64).
- Run
omarchy voxtype install(or click the dictation invitation notification). - Install aborts on the architecture error above.
command -v voxtype→ nothing; F9 does nothing.
Suggested fix
The AUR source package already supports ARM, at the same version:
| Package | arch= | Version |
|---|---|---|
voxtype-bin | ('x86_64') | 0.7.5-1 |
voxtype | ('x86_64' 'aarch64') | 0.7.5-1 |
makedepends are cargo clang cmake git pkgconf shaderc; runtime deps are
identical (alsa-lib curl gcc-libs glibc). Building it on this machine and
running voxtype setup --download --no-post-install + voxtype setup systemd
produces working dictation — the rest of omarchy-voxtype-install is already
architecture-neutral.
So the one-line shape of the fix is to pick the source package when the prebuilt
one cannot run, e.g. gated on the existing omarchy-hw-apple-silicon predicate.
Relationship to the AVX2 issues
This is adjacent to #8312 / #7883 / #7890 and PR #8316, but a distinct failure
mode:
- Those cover x86 CPUs lacking AVX2, where
voxtype-bininstalls and then
SIGILLs at runtime.
- Here the package cannot be installed at all — makepkg refuses on the
architecture declaration, before anything executes.
PR #8316 adds a source-build fallback, which is the right remedy, but it gates onomarchy-hw-x86-64-v3 — a predicate that reads x86 CPU flags from/proc/cpuinfo and is not meaningful on aarch64. That PR mentions no ARM
hardware. If it lands as written, Apple Silicon likely still needs its own gate
(omarchy-hw-apple-silicon, already used by install/hardware/network.sh andomarchy-update-asahi-bundle), and the user-facing message should say
"no prebuilt binary for this architecture" rather than "your CPU lacks AVX2".
Happy to open a PR if the maintainers would like it folded into #8316 or filed
separately.
View raw text
### System details
- Omarchy: 4.0.0.r6673.g5939caf-1
- Hardware: Apple MacBook Air (M1, 2020) — `apple,j313` / `apple,t8103`
- CPU: Apple M1 (aarch64)
- Kernel: 7.1.6-1-1-ARCH (`linux-asahi` 7.1.6.asahi1-1)
- Package: `voxtype-bin` 0.7.5-1
- `omarchy-hw-apple-silicon` → true
### What's wrong?
`bin/omarchy-voxtype-install` installs the prebuilt package unconditionally:
```bash
omarchy-pkg-add wtype voxtype-bin
```
`voxtype-bin` declares `arch=('x86_64')`, so on Apple Silicon it cannot be built
or installed at all:
```text
==> ERROR: voxtype-bin is not available for the 'aarch64' architecture.
```
Dictation is therefore unreachable on every Apple Silicon Omarchy install.
`voxtype` never lands on `PATH`, so the guard in
`default/hypr/bindings/voxtype.lua` never fires:
```lua
if o.cmd_present("voxtype") then
o.bind("SUPER + CTRL + X", "Toggle dictation", "voxtype record toggle")
o.bind("F9", "Start dictation (push-to-talk)", "voxtype record start")
...
end
```
F9 and `SUPER + CTRL + X` silently do nothing, and the `Dictation` bar indicator
stays inert.
Users are actively steered into this dead end:
`install/user/first-run/install-voxtype.hook` raises a **critical** notification
inviting them to "Install voice dictation for Omarchy", whose `--exec` runs the
installer that cannot succeed on this hardware.
### Expected
Either dictation installs successfully on aarch64, or Omarchy declines to offer
it rather than prompting for an install that always fails.
### Steps to reproduce
1. Omarchy on Apple Silicon (Asahi, aarch64).
2. Run `omarchy voxtype install` (or click the dictation invitation notification).
3. Install aborts on the architecture error above.
4. `command -v voxtype` → nothing; F9 does nothing.
### Suggested fix
The AUR **source** package already supports ARM, at the same version:
| Package | `arch=` | Version |
|---|---|---|
| `voxtype-bin` | `('x86_64')` | 0.7.5-1 |
| `voxtype` | `('x86_64' 'aarch64')` | 0.7.5-1 |
`makedepends` are `cargo clang cmake git pkgconf shaderc`; runtime deps are
identical (`alsa-lib curl gcc-libs glibc`). Building it on this machine and
running `voxtype setup --download --no-post-install` + `voxtype setup systemd`
produces working dictation — the rest of `omarchy-voxtype-install` is already
architecture-neutral.
So the one-line shape of the fix is to pick the source package when the prebuilt
one cannot run, e.g. gated on the existing `omarchy-hw-apple-silicon` predicate.
### Relationship to the AVX2 issues
This is adjacent to #8312 / #7883 / #7890 and PR #8316, but a distinct failure
mode:
- Those cover **x86 CPUs lacking AVX2**, where `voxtype-bin` *installs* and then
`SIGILL`s at runtime.
- Here the package **cannot be installed at all** — `makepkg` refuses on the
architecture declaration, before anything executes.
PR #8316 adds a source-build fallback, which is the right remedy, but it gates on
`omarchy-hw-x86-64-v3` — a predicate that reads x86 CPU flags from
`/proc/cpuinfo` and is not meaningful on aarch64. That PR mentions no ARM
hardware. If it lands as written, Apple Silicon likely still needs its own gate
(`omarchy-hw-apple-silicon`, already used by `install/hardware/network.sh` and
`omarchy-update-asahi-bundle`), and the user-facing message should say
"no prebuilt binary for this architecture" rather than "your CPU lacks AVX2".
Happy to open a PR if the maintainers would like it folded into #8316 or filed
separately.
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
- Duplicate ofR-623aarch64: menu offers impossible installs (Spotify, Dropbox) and the floating terminal reports "Done!" on failure· decided by agents · verified
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.