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.
UKI Build Regression: Illegal Instruction (Exit Status 32) on x86-64-v2 Hardware
Reported by acraig78 · filed Feb 14, 2026Closed upstream on 2026-02-22 by ryanrhughes, as a duplicate of #4554 (R-4105). GitHub close reason: duplicate.
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 Core m3-8100Y, Surface Go 2, Omarchy 3.3.3
What's wrong?
UKI Build Regression: Illegal Instruction (Exit Status 32) on x86-64-v2 Hardware
System Info:
CPU: Intel Core m3-8100Y (Surface Go 2)
Architecture Level: x86-64-v2 (AVX/AVX2 flags missing/disabled in firmware)
Kernel: Working on 6.18.3-arch1-1 | Fails on 6.18.7
While updating to kernel 6.18.7, the post-transaction hooks for building the Unified Kernel Image (UKI) fail with an "illegal instruction" error. This results in an exit status 32 during the systemd-remount-fs stage upon reboot, forcing the system into Emergency Mode.
Technical Details:
A manual trigger of mkinitcpio (e.g., via intel-ucode reinstall) works perfectly on kernel 6.18.3.
The failure occurs during the 6.18.7 update's Updating linux initcpios phase.
lscpu confirms the hardware is limited to x86-64-v2.
The crash is likely caused by a toolchain dependency (likely zstd, mkinitcpio, or ukify) in the latest update being compiled with x86-64-v3 (AVX2) instructions.
Steps to Reproduce:
Use an Intel m3-8100Y or similar v2-only CPU.
Attempt to upgrade to kernel 6.18.7-arch1-1.
Observe the trap invalid opcode or exit status 32 during the UKI build hooks.
View raw text
### System details Intel Core m3-8100Y, Surface Go 2, Omarchy 3.3.3 ### What's wrong? UKI Build Regression: Illegal Instruction (Exit Status 32) on x86-64-v2 Hardware System Info: CPU: Intel Core m3-8100Y (Surface Go 2) Architecture Level: x86-64-v2 (AVX/AVX2 flags missing/disabled in firmware) Kernel: Working on 6.18.3-arch1-1 | Fails on 6.18.7 While updating to kernel 6.18.7, the post-transaction hooks for building the Unified Kernel Image (UKI) fail with an "illegal instruction" error. This results in an exit status 32 during the systemd-remount-fs stage upon reboot, forcing the system into Emergency Mode. Technical Details: A manual trigger of mkinitcpio (e.g., via intel-ucode reinstall) works perfectly on kernel 6.18.3. The failure occurs during the 6.18.7 update's Updating linux initcpios phase. lscpu confirms the hardware is limited to x86-64-v2. The crash is likely caused by a toolchain dependency (likely zstd, mkinitcpio, or ukify) in the latest update being compiled with x86-64-v3 (AVX2) instructions. Steps to Reproduce: Use an Intel m3-8100Y or similar v2-only CPU. Attempt to upgrade to kernel 6.18.7-arch1-1. Observe the trap invalid opcode or exit status 32 during the UKI build hooks.
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.