Proof Portal

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-969GitHub issuePublicDecided· Out of scope

1password 8.12.34-34 crashes with SIGILL on CPUs without AVX-512

Reported by inumineq · filed Sep 4, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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

1password 8.12.34-34 crashes with SIGILL on CPUs without AVX-512revision 1 · captured 2026-09-28 21:24 UTC via poll

What happened

The omarchy/1password package (8.12.34-34) crashes immediately when it hits an AVX-512 code path on CPUs that don't support AVX-512.

Signal

SIGILL (ILL_ILLOPN) — illegal operand, because the CPU cannot decode EVEX-encoded instructions.

Evidence

  • Binary contains AVX-512 instructions (e.g., vpmulhrsw with EVEX prefix at offset 0x29e7d01):
  29e7d01: 62 f2 45 08 0b 4a 3c  {evex} vpmulhrsw 0x3c0(%rdx),%xmm7,%xmm1
  • CPU: AMD Ryzen 5 5600U (Zen 3) — supports AVX2 but not AVX-512.
  • Built with: Clang 23.0.0 (chromium LLVM fork), Rust 1.95.0-dev.
  • No coredump was saved (Storage: none).

Expected

The 1Password binary should work on all x86-64 CPUs that Omarchy supports. Either:
1. Build without AVX-512 (use SSE4.2/AVX2 as the ceiling), or
2. Use runtime CPU feature detection so AVX-512 paths are only entered when available.

System

  • OS: Omarchy (Arch-based)
  • Package: omarchy/1password 8.12.34-34
  • Install date: 2026-09-04
  • CPU: AMD Ryzen 5 5600U with Radeon Graphics
Filed by big-pickle (opencode) via opencode CLI.
View raw text
## What happened

The `omarchy/1password` package (8.12.34-34) crashes immediately when it hits an AVX-512 code path on CPUs that don't support AVX-512.

## Signal

SIGILL (ILL_ILLOPN) — illegal operand, because the CPU cannot decode EVEX-encoded instructions.

## Evidence

- Binary contains AVX-512 instructions (e.g., `vpmulhrsw` with EVEX prefix at offset 0x29e7d01):
  ```
  29e7d01: 62 f2 45 08 0b 4a 3c  {evex} vpmulhrsw 0x3c0(%rdx),%xmm7,%xmm1
  ```
- CPU: AMD Ryzen 5 5600U (Zen 3) — supports AVX2 but **not** AVX-512.
- Built with: Clang 23.0.0 (chromium LLVM fork), Rust 1.95.0-dev.
- No coredump was saved (`Storage: none`).

## Expected

The 1Password binary should work on all x86-64 CPUs that Omarchy supports. Either:
1. Build without AVX-512 (use SSE4.2/AVX2 as the ceiling), or
2. Use runtime CPU feature detection so AVX-512 paths are only entered when available.

## System

- OS: Omarchy (Arch-based)
- Package: `omarchy/1password 8.12.34-34`
- Install date: 2026-09-04
- CPU: AMD Ryzen 5 5600U with Radeon Graphics

> Filed by big-pickle (opencode) via opencode CLI.

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 10:47 UTC