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.
omarchy install editor zed fails on aarch64: 'zed' package not found
Reported by rafaelguariento · filed Sep 20, 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 editor zed (via the install menu or omarchy-install-editor-zed) fails on aarch64 with:
error: package 'zed' was not foundNeither zed nor omazed gets installed, because the script does a single atomic transaction:
omarchy-pkg-add zed omazed
# -> pacman -S --noconfirm --needed zed omazedSince zed isn't resolvable, the whole pacman transaction aborts and omazed (which is available for aarch64, arch=any) never gets installed either.
Root cause
The omarchy repo (https://pkgs.omarchy.org/edge/$arch) does not currently publish a zed package for the aarch64 architecture — only omazed (arch=any) is present. pacman -Si zed on aarch64 returns "package 'zed' was not found", while pacman -Si omazed succeeds.
Zed itself has no packaging problem here — the upstream project ships official aarch64 Linux builds (glibc >= 2.35 required; this system has 2.43) and installs/runs fine via curl -f https://zed.dev/install.sh | sh.
Expected
omarchy install editor zed should succeed on aarch64, either by:
- Publishing a zed package for aarch64 in the omarchy repo, or
- Falling back to Zed's official install script for architectures where the repo package isn't available.
Steps to reproduce
- On an aarch64 Omarchy install, run
omarchy install editor zed(or select "Zed" from the install menu). - Observe the pacman error and that neither
zednoromazedend up installed.
System details
omarchy version: 4.0.0.r2120.g66a33c3-1- Architecture: aarch64
ldd --version: glibc 2.43pacman -Si zedon this system:error: package 'zed' was not foundpacman -Si omazedon this system: succeeds,Architecture: any, from repoomarchy
Workaround used
- Installed Zed manually via
curl -f https://zed.dev/install.sh | sh(works fine on aarch64). - Installed
omazedseparately:sudo pacman -S --noconfirm --needed omazed. - Ran
omazed setupto wire up theme sync.
View raw text
## What happened Running `omarchy install editor zed` (via the install menu or `omarchy-install-editor-zed`) fails on aarch64 with: ``` error: package 'zed' was not found ``` Neither `zed` nor `omazed` gets installed, because the script does a single atomic transaction: ```bash omarchy-pkg-add zed omazed # -> pacman -S --noconfirm --needed zed omazed ``` Since `zed` isn't resolvable, the whole pacman transaction aborts and `omazed` (which *is* available for aarch64, arch=any) never gets installed either. ## Root cause The `omarchy` repo (`https://pkgs.omarchy.org/edge/$arch`) does not currently publish a `zed` package for the `aarch64` architecture — only `omazed` (arch=any) is present. `pacman -Si zed` on aarch64 returns "package 'zed' was not found", while `pacman -Si omazed` succeeds. Zed itself has no packaging problem here — the upstream project ships official aarch64 Linux builds (glibc >= 2.35 required; this system has 2.43) and installs/runs fine via `curl -f https://zed.dev/install.sh | sh`. ## Expected `omarchy install editor zed` should succeed on aarch64, either by: - Publishing a `zed` package for aarch64 in the `omarchy` repo, or - Falling back to Zed's official install script for architectures where the repo package isn't available. ## Steps to reproduce 1. On an aarch64 Omarchy install, run `omarchy install editor zed` (or select "Zed" from the install menu). 2. Observe the pacman error and that neither `zed` nor `omazed` end up installed. ## System details - `omarchy version`: 4.0.0.r2120.g66a33c3-1 - Architecture: aarch64 - `ldd --version`: glibc 2.43 - `pacman -Si zed` on this system: `error: package 'zed' was not found` - `pacman -Si omazed` on this system: succeeds, `Architecture: any`, from repo `omarchy` ## Workaround used 1. Installed Zed manually via `curl -f https://zed.dev/install.sh | sh` (works fine on aarch64). 2. Installed `omazed` separately: `sudo pacman -S --noconfirm --needed omazed`. 3. Ran `omazed setup` to wire up theme sync.
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
- Related PRpr/12932· confirmed
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 16:36 UTC