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.
GeForce NOW installer aborts through host FEX on aarch64 with 16 KiB pages
Reported by alexpomsft · filed Oct 8, 2026 · open at source
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
What happened
Running omarchy-install-gaming-geforce-now on an aarch64 machine with 16 KiB host pages crashes /usr/bin/FEX with SIGABRT before GeForce NOW is installed.
The script downloads NVIDIA's x86-64 GeForceNOWSetup.bin to /tmp, makes it executable, and runs it directly. The enabled host FEX-x86_64 binfmt registration redirects execution to /usr/bin/FEX, which cannot run in this host-page-size environment. The same direct-execution path is present in the current upstream script.
Steps to reproduce
- Use an aarch64 Omarchy machine with 16 KiB host pages and enabled FEX binfmt registration.
- Run
omarchy-install-gaming-geforce-now. - The installer aborts through FEX; no GeForce NOW application is installed.
Expected behavior
The installer should detect this unsupported execution environment and show a clear error instead of launching an incompatible binary. If a supported ARM/microVM installation path exists, use that path instead. I have not tested GeForce NOW inside muvm and am not claiming it works there.
Environment
- Omarchy:
4.0.3rc4-1 - Distribution: Arch Linux ARM
- Kernel:
7.1.12-2-12.2-sep-ARCH - Hardware: Apple M2 Max
- Architecture:
aarch64 - Host page size:
16384(getconf PAGESIZE) - FEX-Emu:
2604-1, fromasahi-alarm - muvm:
0.6.0-1 - Flatpak:
1:1.18.4-1
Diagnostics
Two installer attempts on 2026-10-08 at 14:39:36 and 14:44:13 CEST produced the same SIGABRT stack. The recorded command line was:
/usr/bin/FEX ./GeForceNOWSetup.bin ./GeForceNOWSetup.binThe core contains one thread, with these relevant frames:
abort
__gnu_cxx::__verbose_terminate_handler()
std::terminate()
__cxa_allocate_exception
operator new(unsigned long)
FEX + 0x1d7980
FEX + 0x1d5bd0
FEX + 0x91e38A direct diagnostic FEX --help also aborted with:
<jemalloc>: Unsupported system page size
terminate called without an active exceptionFEX-x86_64 binfmt registration is enabled, uses /usr/bin/FEX, and has flags POCF. The downloaded installer is an x86-64 ELF. About 50 GiB of memory was available when checked, no kernel OOM kill was recorded, and address-space/data limits were unlimited.
Standard diagnostics were collected using /usr/bin/omarchy-debug --no-sudo --print; only relevant system details are included here. No core files, private process environment, or full journal are attached.
Scope and related reports
FEX's page-size limitation is already documented at https://asahilinux.org/docs/sw/broken-software/ and discussed in https://github.com/asahi-alarm/PKGBUILDs/issues/2. This report concerns Omarchy's installer invoking that unsupported direct-host path, not a request for FEX to support 16 KiB pages.
Related: https://github.com/omacom/omarchy/issues/8645 concerns architecture/package-availability checks in install menus, but does not cover this NVIDIA installer/FEX abort.
Filed by GPT-6.1 Sol via GitHub Copilot CLI.
View raw text
## What happened Running `omarchy-install-gaming-geforce-now` on an aarch64 machine with 16 KiB host pages crashes `/usr/bin/FEX` with SIGABRT before GeForce NOW is installed. The script downloads NVIDIA's x86-64 `GeForceNOWSetup.bin` to `/tmp`, makes it executable, and runs it directly. The enabled host `FEX-x86_64` binfmt registration redirects execution to `/usr/bin/FEX`, which cannot run in this host-page-size environment. The same direct-execution path is present in the current upstream script. ## Steps to reproduce 1. Use an aarch64 Omarchy machine with 16 KiB host pages and enabled FEX binfmt registration. 2. Run `omarchy-install-gaming-geforce-now`. 3. The installer aborts through FEX; no GeForce NOW application is installed. ## Expected behavior The installer should detect this unsupported execution environment and show a clear error instead of launching an incompatible binary. If a supported ARM/microVM installation path exists, use that path instead. I have not tested GeForce NOW inside muvm and am not claiming it works there. ## Environment - Omarchy: `4.0.3rc4-1` - Distribution: Arch Linux ARM - Kernel: `7.1.12-2-12.2-sep-ARCH` - Hardware: Apple M2 Max - Architecture: `aarch64` - Host page size: `16384` (`getconf PAGESIZE`) - FEX-Emu: `2604-1`, from `asahi-alarm` - muvm: `0.6.0-1` - Flatpak: `1:1.18.4-1` ## Diagnostics Two installer attempts on 2026-10-08 at 14:39:36 and 14:44:13 CEST produced the same SIGABRT stack. The recorded command line was: ```text /usr/bin/FEX ./GeForceNOWSetup.bin ./GeForceNOWSetup.bin ``` The core contains one thread, with these relevant frames: ```text abort __gnu_cxx::__verbose_terminate_handler() std::terminate() __cxa_allocate_exception operator new(unsigned long) FEX + 0x1d7980 FEX + 0x1d5bd0 FEX + 0x91e38 ``` A direct diagnostic `FEX --help` also aborted with: ```text <jemalloc>: Unsupported system page size terminate called without an active exception ``` `FEX-x86_64` binfmt registration is enabled, uses `/usr/bin/FEX`, and has flags `POCF`. The downloaded installer is an x86-64 ELF. About 50 GiB of memory was available when checked, no kernel OOM kill was recorded, and address-space/data limits were unlimited. Standard diagnostics were collected using `/usr/bin/omarchy-debug --no-sudo --print`; only relevant system details are included here. No core files, private process environment, or full journal are attached. ## Scope and related reports FEX's page-size limitation is already documented at https://asahilinux.org/docs/sw/broken-software/ and discussed in https://github.com/asahi-alarm/PKGBUILDs/issues/2. This report concerns Omarchy's installer invoking that unsupported direct-host path, not a request for FEX to support 16 KiB pages. Related: https://github.com/omacom/omarchy/issues/8645 concerns architecture/package-availability checks in install menus, but does not cover this NVIDIA installer/FEX abort. Filed by GPT-6.1 Sol via GitHub Copilot 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 22:53 UTC