## Summary

On aarch64, the Omarchy menu offers package installs that can never succeed, and the floating-terminal wrapper reports `Done!` when they fail. Together these produce a silent infinite loop: the user picks "Install → Service → Spotify", sees `Done!`, and Spotify is still not installed — every time, with no indication anything went wrong.

Two separate defects, filed together because the second is what makes the first invisible. Happy to split them if you'd prefer.

---

### Bug 1 — menu offers installs that are impossible on the running architecture

`omarchy-menu.jsonc` gates the Spotify entry purely on whether the package is present:

```jsonc
"install.service.spotify": {
  "icon":"󰓇","label":"Spotify",
  "when":"! omarchy-pkg-present spotify",
  "action":"omarchy-launch-floating-terminal-with-presentation omarchy-install-service-spotify"
}
```

`spotify` is x86_64-only — the AUR PKGBUILD is `arch=('x86_64')` and its source is an `amd64` .deb from `repository.spotify.com`. On aarch64 it is simply not in any repo:

```
$ pacman -Si spotify
error: package 'spotify' was not found
```

So `omarchy-install-service-spotify` fails at `omarchy-pkg-add spotify`, `set -e` aborts the script before the `setsid uwsm-app -- /usr/bin/spotify` line, the package is never installed, the `when` guard stays true, and the entry is offered again forever.

**This is not Spotify-specific.** Auditing every `omarchy-install-service-*` entry against the aarch64 repos:

| Service | Package | Available on aarch64 |
|---|---|---|
| spotify | `spotify` | **no** |
| dropbox | `dropbox`, `dropbox-cli`, `nautilus-dropbox`, `libappindicator-gtk3` | **no** |
| signal | `signal-desktop` | yes |
| tailscale | `tailscale` | yes |
| nordvpn | `nordvpn-bin` | yes |
| once | `once-bin` | yes |

Dropbox has exactly the same failure mode. There is currently no architecture gating anywhere in the menu — `grep -c 'uname\|x86_64\|aarch64' omarchy-menu.jsonc` returns `0`.

Since `when` is arbitrary shell, a gate is cheap. Either make it architecture-aware, or better, gate on actual installability so it self-maintains:

```jsonc
"when":"! omarchy-pkg-present spotify && pacman -Si spotify &>/dev/null"
```

### Bug 2 — the presentation wrapper reports success for failed commands

`omarchy-launch-floating-terminal-with-presentation`:

```bash
presentation_script="omarchy-show-logo; $cmd; if (( \$? != 130 )); then omarchy-show-done; fi"
```

`omarchy-show-done` prints a green `● Done!` for **every** exit status except `130` (Ctrl-C). A command that fails with exit 1 is presented identically to one that succeeded. That is what turns Bug 1 from an obvious error into a mystery — the pacman error does scroll past above the prompt, but the last thing on screen is a green `Done!`.

Suggested fix — branch on the status rather than only excluding `130`:

```bash
presentation_script="omarchy-show-logo; $cmd; status=\$?; if (( status == 130 )); then :; elif (( status == 0 )); then omarchy-show-done; else omarchy-show-failed \$status; fi"
```

---

## Steps to reproduce

On any aarch64 Omarchy install:

1. `SUPER + SPACE`, type `spotify`, select **Install → Service → Spotify**
2. Enter the sudo password
3. Observe the green `Done!`
4. `pacman -Q spotify` → `error: package 'spotify' was not found`
5. Repeat from step 1 — the entry is still offered, with the identical outcome

## Expected

Either the entry is not offered on an architecture where the package cannot be installed, or the install failure is surfaced plainly instead of being reported as `Done!`.

## Actual

The install fails silently and the menu entry loops forever.

## System

| | |
|---|---|
| Omarchy | `4.0.1.r6114.g1e06f6fa6bec-1` |
| Kernel | `7.2.0-1-aarch64-ARCH` |
| Arch | `aarch64` (Apple Silicon, virtualised) |
| Hyprland | `0.56.1` |
| Repos | `core extra alarm aur` |

## Side note

For anyone landing here looking for Spotify on aarch64: the web player is not a workaround either, since there is no Widevine CDM for `Linux_aarch64` in either Chromium (the ALARM build ships none) or Firefox (Mozilla's GMP service offers only OpenH264 for that platform). The working options are the native librespot-based clients in `extra` — `spotify-player` or `ncspot` — both of which require Spotify Premium. Note that the `spotify-player` package installs its binary as `spotify_player`, with an underscore.