Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4691GitHub issuePublicReceived

Dictation (Voxtype) leaves broken install on CPUs without AVX2 instead of failing gracefully

Reported by ironbract · filed Aug 25, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7883 (R-1550). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Dictation (Voxtype) leaves broken install on CPUs without AVX2 instead of failing gracefullyrevision 1 · captured 2026-10-04 12:03 UTC via poll

Summary

Enabling dictation on a CPU that predates the AVX2/x86-64-v3 baseline fails with FATAL: Illegal CPU instruction (SIGILL), but the install script leaves Voxtype installed in a broken state instead of rolling back or cleaning up.

Steps to reproduce

  1. On a machine with a pre-Haswell CPU (no AVX2), enable dictation via Install > AI > Dictation.
  2. Try to invoke dictation (Super + Ctrl + X).
  3. Voxtype crashes with:
   FATAL: Illegal CPU instruction (SIGILL)

Expected behavior

Since Voxtype's prebuilt binaries target the x86-64-v3 baseline (AVX2, FMA, BMI1/2, F16C, MOVBE), the installer should either:
- detect CPU support for the required instruction set before installing, and refuse/warn up front, or
- build from source for CPUs lacking AVX2 (as Voxtype's own docs suggest, via -C target-cpu=native), or
- at minimum, if the installed binary can't run, clean up the failed install (remove the broken binary/service/config) rather than leaving it in place.

Actual behavior

Voxtype ends up installed but non-functional — running it just SIGILLs every time. The install script doesn't detect the incompatibility or clean up afterward, leaving a broken package on disk.

Environment

  • CPU: Intel Core i7-3520M (Ivy Bridge — no AVX2 support)
  • Omarchy version: 4.0.1-1
  • Relevant related issues: #4605 (UKI Build Regression: Illegal Instruction on x86-64-v2 hardware — same AVX2 baseline mismatch, different component)

Additional context

This is likely the same underlying x86-64-v3 vs. x86-64-v2 CPU baseline mismatch seen in #4605, just surfacing through Voxtype/dictation instead of the UKI build tooling. Worth considering a general CPU-baseline check somewhere in the installer given it's now bitten at least two components.

View raw text
### Summary

Enabling dictation on a CPU that predates the AVX2/x86-64-v3 baseline fails with `FATAL: Illegal CPU instruction (SIGILL)`, but the install script leaves Voxtype installed in a broken state instead of rolling back or cleaning up.

### Steps to reproduce

1. On a machine with a pre-Haswell CPU (no AVX2), enable dictation via Install > AI > Dictation.
2. Try to invoke dictation (Super + Ctrl + X).
3. Voxtype crashes with:
   ```
   FATAL: Illegal CPU instruction (SIGILL)
   ```

### Expected behavior

Since Voxtype's prebuilt binaries target the x86-64-v3 baseline (AVX2, FMA, BMI1/2, F16C, MOVBE), the installer should either:
- detect CPU support for the required instruction set before installing, and refuse/warn up front, or
- build from source for CPUs lacking AVX2 (as Voxtype's own docs suggest, via `-C target-cpu=native`), or
- at minimum, if the installed binary can't run, clean up the failed install (remove the broken binary/service/config) rather than leaving it in place.

### Actual behavior

Voxtype ends up installed but non-functional — running it just SIGILLs every time. The install script doesn't detect the incompatibility or clean up afterward, leaving a broken package on disk.

### Environment

- CPU: Intel Core i7-3520M (Ivy Bridge — no AVX2 support)
- Omarchy version: 4.0.1-1
- Relevant related issues: #4605 (UKI Build Regression: Illegal Instruction on x86-64-v2 hardware — same AVX2 baseline mismatch, different component)

### Additional context

This is likely the same underlying x86-64-v3 vs. x86-64-v2 CPU baseline mismatch seen in #4605, just surfacing through Voxtype/dictation instead of the UKI build tooling. Worth considering a general CPU-baseline check somewhere in the installer given it's now bitten at least two components.

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.

No decision has been recorded yet.