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.
1password crashes with SIGILL (ILL_ILLOPN) on first launch after fresh install
Reported by pgremo · filed Aug 26, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7870 (R-1556). GitHub close reason: completed.
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
System details
Intel(R) Core(TM) i9-14900KF ,GeForce RTX 4080 SUPER
What's wrong?
What happened
1Password v8.12.34-34 from omarchy/1password crashes immediately on first
launch after a clean install via omarchy-install-service-1password.
Signal
SIGILL (signal 4), si_code: ILL_ILLOPN (illegal operand).
Kernel trap:
traps: 1password[8088] trap invalid opcode ip:55c08be52195 sp:7ffd691a1100 error:0
in 1password[70ea195,55c0873e9000+9aa1000]
Fault is inside the main 1password binary, not a shared library.
Timeline
- 16:27:42 —
pacman -S --noconfirm --needed 1password 1password-cli - 16:27:56 — 1password launched
- 16:28:31 — SIGILL crash (35s after launch)
System
- Arch Linux, kernel 6.x
- CPU: Intel i9-14900KF (has AVX-512, AVX-VNNI, etc.)
- RAM: 32 GiB, 23 GiB free at time of crash
- No OOM kills, no resource exhaustion
- Only one crash in log — not a repeat
What I tried
- No core dump available (core dumping disabled by resource limits)
- Package integrity check (
pacman -Qii) reports OK - No user data existed yet — first run, nothing lost
Notes
Packager is listed as "Unknown Packager". The binary may have a build or
packaging issue specific to this version. A symbolized backtrace would
confirm the exact illegal instruction.
View raw text
### System details
Intel(R) Core(TM) i9-14900KF ,GeForce RTX 4080 SUPER
### What's wrong?
## What happened
1Password v8.12.34-34 from `omarchy/1password` crashes immediately on first
launch after a clean install via `omarchy-install-service-1password`.
## Signal
SIGILL (signal 4), si_code: ILL_ILLOPN (illegal operand).
Kernel trap:
traps: 1password[8088] trap invalid opcode ip:55c08be52195 sp:7ffd691a1100 error:0
in 1password[70ea195,55c0873e9000+9aa1000]
Fault is inside the main 1password binary, not a shared library.
## Timeline
- 16:27:42 — `pacman -S --noconfirm --needed 1password 1password-cli`
- 16:27:56 — 1password launched
- 16:28:31 — SIGILL crash (35s after launch)
## System
- Arch Linux, kernel 6.x
- CPU: Intel i9-14900KF (has AVX-512, AVX-VNNI, etc.)
- RAM: 32 GiB, 23 GiB free at time of crash
- No OOM kills, no resource exhaustion
- Only one crash in log — not a repeat
## What I tried
- No core dump available (core dumping disabled by resource limits)
- Package integrity check (`pacman -Qii`) reports OK
- No user data existed yet — first run, nothing lost
## Notes
Packager is listed as "Unknown Packager". The binary may have a build or
packaging issue specific to this version. A symbolized backtrace would
confirm the exact illegal instruction.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.