Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-203GitHub issuePublicReceived

Apps submenu empty ("Nothing here yet") after upgrade to 4.0.4; downgrade to 4.0.2 restores it

Reported by RistoWieland · filed Sep 22, 2026 · open at source

In the audited area (menu) — decided by agents · verified. Not validated yet.

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?
AreaIn the audited areamenu· 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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: in the audited area (menu) — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Apps submenu empty ("Nothing here yet") after upgrade to 4.0.4; downgrade to 4.0.2 restores itrevision 1 · captured 2026-09-28 21:23 UTC via poll

Summary

After upgrading omarchy 4.0.2 → 4.0.4, the Apps submenu of the omarchy menu (SUPER+SPACE → Apps) is completely empty and shows "Nothing here yet". The rest of the menu is fine — the root menu and all other submenus render normally. Downgrading `omarchy` + `omarchy-settings` back to 4.0.2 immediately restores the Apps list. Everything that depends on the shell's appLibrary (the Apps submenu) is affected; nothing else is.

Environment

  • omarchy: bug present on 4.0.4-1 (upgraded from 4.0.2-1); currently pinned back to 4.0.2-1 as a workaround
  • quickshell: 0.3.1-1 (extra)
  • kernel: 7.2.5-3-omarchy
  • CPU: Intel Core i5-1340P · GPU: Intel Iris Xe (Raptor Lake-P)
  • LUKS full-disk-encrypted, UKI/Limine boot

Steps to reproduce

  1. On 4.0.4, open the menu (SUPER+SPACE) → navigate to Apps.
  2. The list is empty: "Nothing here yet".

Expected vs. actual

  • Expected: the installed applications are listed (as on 4.0.2).
  • Actual: empty. omarchy menu ping/refresh both return ok; omarchy-restart-shell and a full reboot do not help. Downgrading to 4.0.2 does.

What I verified (to rule things out)

  • Not DesktopEntries: a standalone quickshell -p probe with a persistent binding on DesktopEntries.applications.values returns 87 entries. The running shell also logs 120 Found desktop entry lines.
  • Not the hidden-entry filter: services/hidden-entries.sh + default/omarchy/launcher.hides together leave ~50 apps visible.
  • Not user config: temporarily removing ~/.config/omarchy/extensions/omarchy-menu.jsonc and refreshing — Apps still empty.
  • Not qt6-base 6.11.2-2→-3 (which upgraded in the same transaction): tested and ruled out.
  • Root menu + other submenus render fine — only the appLibrary-backed Apps list is empty. mergeAppRows() produces no rows, without throwing (no error in the qslog).

Hypothesis (not confirmed)

4.0.4 introduced a plugin shell-API proxy layer that did not exist in 4.0.2 — shell/services/PluginShellApi.qml and shell/services/PluginAppLibraryApi.qml, wired via pluginShellFor() / createScopedPluginShell() in shell.qml. In 4.0.2 the menu received shell: shell directly (real AppLibrary). My best guess is that appLibrary no longer reaches the omarchy.menu plugin through this new proxy, so Menu.qml's mergeAppRows() bails at if (!root.appLibrary) return. I could not pin the exact reason with certainty (the code paths look like they should deliver a non-null proxy), so this may be environment-specific rather than universal — happy to gather more diagnostics.

Workaround

Downgrade and pin:

sudo pacman -U /var/cache/pacman/pkg/omarchy-4.0.2-1-any.pkg.tar.zst \
               /var/cache/pacman/pkg/omarchy-settings-4.0.2-1-any.pkg.tar.zst
# then IgnorePkg = omarchy omarchy-settings in /etc/pacman.conf
omarchy-restart-shell

I can attach a screenshot of the empty Apps popup and the full omarchy debug log on request.

View raw text
## Summary

After upgrading **omarchy 4.0.2 → 4.0.4**, the **Apps** submenu of the omarchy menu (SUPER+SPACE → Apps) is completely empty and shows *"Nothing here yet"*. The rest of the menu is fine — the root menu and all other submenus render normally. **Downgrading `omarchy` + `omarchy-settings` back to 4.0.2 immediately restores the Apps list.** Everything that depends on the shell's `appLibrary` (the Apps submenu) is affected; nothing else is.

## Environment

- omarchy: bug present on **4.0.4-1** (upgraded from 4.0.2-1); currently pinned back to 4.0.2-1 as a workaround
- quickshell: 0.3.1-1 (extra)
- kernel: 7.2.5-3-omarchy
- CPU: Intel Core i5-1340P · GPU: Intel Iris Xe (Raptor Lake-P)
- LUKS full-disk-encrypted, UKI/Limine boot

## Steps to reproduce

1. On 4.0.4, open the menu (SUPER+SPACE) → navigate to **Apps**.
2. The list is empty: *"Nothing here yet"*.

## Expected vs. actual

- **Expected:** the installed applications are listed (as on 4.0.2).
- **Actual:** empty. `omarchy menu ping`/`refresh` both return `ok`; `omarchy-restart-shell` and a full reboot do **not** help. Downgrading to 4.0.2 does.

## What I verified (to rule things out)

- **Not DesktopEntries:** a standalone `quickshell -p` probe with a persistent binding on `DesktopEntries.applications.values` returns **87** entries. The running shell also logs 120 `Found desktop entry` lines.
- **Not the hidden-entry filter:** `services/hidden-entries.sh` + `default/omarchy/launcher.hides` together leave ~50 apps visible.
- **Not user config:** temporarily removing `~/.config/omarchy/extensions/omarchy-menu.jsonc` and refreshing — Apps still empty.
- **Not qt6-base 6.11.2-2→-3** (which upgraded in the same transaction): tested and ruled out.
- **Root menu + other submenus render fine** — only the `appLibrary`-backed Apps list is empty. `mergeAppRows()` produces no rows, without throwing (no error in the qslog).

## Hypothesis (not confirmed)

4.0.4 introduced a plugin shell-API proxy layer that did not exist in 4.0.2 — `shell/services/PluginShellApi.qml` and `shell/services/PluginAppLibraryApi.qml`, wired via `pluginShellFor()` / `createScopedPluginShell()` in `shell.qml`. In 4.0.2 the menu received `shell: shell` directly (real `AppLibrary`). My best guess is that `appLibrary` no longer reaches the `omarchy.menu` plugin through this new proxy, so `Menu.qml`'s `mergeAppRows()` bails at `if (!root.appLibrary) return`. I could not pin the exact reason with certainty (the code paths *look* like they should deliver a non-null proxy), so this may be environment-specific rather than universal — happy to gather more diagnostics.

## Workaround

Downgrade and pin:

```
sudo pacman -U /var/cache/pacman/pkg/omarchy-4.0.2-1-any.pkg.tar.zst \
               /var/cache/pacman/pkg/omarchy-settings-4.0.2-1-any.pkg.tar.zst
# then IgnorePkg = omarchy omarchy-settings in /etc/pacman.conf
omarchy-restart-shell
```

I can attach a screenshot of the empty Apps popup and the full `omarchy debug` log on request.

Also reported as

This defect is tracked under R-203 (filed Sep 22, 2026). 1 other report describes the same defect.

Earliest report of this defect: R-405 (filed Sep 17, 2026).

  1. Sep 22, 2026R-203 · this report— tracked here
  2. ·Decided by agents · verified

    Open upstream.

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/13469· confirmed
  • Related PRpr/13642· 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.

  • Decided by agents · verified: in the audited area (menu)

The outcome (valid, duplicate, not a bug, …) is not decided yet.