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.
Third-party menus lose app-library access after Instantiator manifest conversion
Reported by DanielLemky · filed Sep 10, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #10661 (R-860). GitHub close reason: completed.
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 MacBook Pro, Core i9-9880H
- Intel UHD Graphics 630 and AMD Radeon Pro 5500M
- Omarchy
4.0.3-1 - Quickshell
0.3.1-1 - Hyprland
0.56.2-2 - Omalaunch
v0.4.0, commit59b7ecd
Failure
The new plugin API gives a valid third-party menu appLibrary: null after its manifest passes through the panel Instantiator. The installed application list and application search are empty. Static menu commands still work. The stock first-party menu displays applications correctly on the same machine.
This was first reported at https://github.com/DanielLemky/omalaunch/issues/68. I reproduced it on a second machine with the same package versions.
Reproduction
- Use Omarchy 4.0.3 and Quickshell 0.3.1.
- Install and enable Omalaunch v0.4.0. Its manifest declares
"kinds": ["menu", "bar-widget"]. - Open its Apps submenu or search for an installed application.
- Disable Omalaunch and enable
omarchy.menufor comparison.
Expected: the third-party menu receives the app-library API promised to plugins with the menu kind.
Actual: its injected PluginShellApi has the correct plugin ID, but appLibrary is null. The stock menu works because it receives the full shell, not this API.
Confirmed cause
In shell/shell.qml:
computePanelEntries()puts registry manifests in the panel model.Instantiatorconverts the nestedkindsarray to a QMLV4Sequence.- The loader calls
pluginShellFor(panelEntry.manifest)with that converted value. manifestHasKind()requiresArray.isArray(manifest.kinds). This returns false for the sequence, althoughkinds.indexOf("menu")returns 0.createScopedPluginShell()therefore creates an API without app-library access.
A previous lookup with the original registry manifest can first create a valid menu API. The delegate lookup then changes the capability profile to no-menu, which revokes that API and replaces it.
The plugin's separately injected public manifest looks correct because publicPluginManifest() copies it through JSON. That converts the sequence back to an array, but it is too late for the capability check.
The following small test reproduces the conversion without a desktop window or Omalaunch. Save it as shell.qml and run QT_QPA_PLATFORM=offscreen quickshell -p shell.qml:
import QtQuick
import QtQml.Models
import Quickshell
ShellRoot {
id: root
property var manifest: ({ id: "example.menu", kinds: ["menu"] })
property var entries: [{ manifest: root.manifest }]
Instantiator {
model: root.entries
delegate: QtObject {
required property var modelData
Component.onCompleted: {
var kinds = modelData.manifest.kinds
console.log("delegate", Array.isArray(kinds),
Object.prototype.toString.call(kinds), kinds.indexOf("menu"))
}
}
}
Component.onCompleted: {
console.log("registry", Array.isArray(manifest.kinds))
Qt.callLater(Qt.quit)
}
}Output on Quickshell 0.3.1:
delegate false [object V4Sequence] 0
registry trueTested correction
Resolve the plugin ID to the registry's validated manifest inside pluginShellFor(), before the trust and capability checks. Do not use the delegate's converted manifest for those decisions:
function pluginShellFor(manifest) {
var key = String(manifest && manifest.id || "")
if (!key) return null
var registeredManifest = shell.pluginRegistry.installedPlugins[key]
if (!registeredManifest) return null
if (registeredManifest.__isFirstParty) return shell
return shell.createScopedPluginShell(registeredManifest, key, true,
shell.pluginHasBarCapabilities(registeredManifest))
}I tested this correction in a separate copy of the packaged 4.0.3 shell, with clean Omalaunch v0.4.0. Installed applications appeared. Search from Apps and from the root menu worked. Selecting Alacritty opened a new Alacritty window. Reopening the menu and rescanning plugins retained application access.
An earlier diagnostic test returned 98 application rows after the type check was corrected. The original path returned zero rows because the library was null.
No packaged files were edited. The standard shell and plugin were restored after testing. Screenshots and a private omarchy debug --no-sudo --print log were collected; the complete system log is not included because it contains unrelated machine details.
Scope
AppLibrary.qml, AppSearch.js, and the stock menu QML did not change between v4.0.2 and v4.0.3. The relevant change is the new third-party API injection from #9618, included in the 4.0.3 backport #10733.
This is separate from Omalaunch's use of the raw-only iconIndexChanged signal. Correcting the app-library grant restores applications without changing Omalaunch. The icon-refresh compatibility change is being handled separately in Omalaunch.
View raw text
## System details
- Intel MacBook Pro, Core i9-9880H
- Intel UHD Graphics 630 and AMD Radeon Pro 5500M
- Omarchy `4.0.3-1`
- Quickshell `0.3.1-1`
- Hyprland `0.56.2-2`
- Omalaunch `v0.4.0`, commit `59b7ecd`
## Failure
The new plugin API gives a valid third-party menu `appLibrary: null` after its manifest passes through the panel `Instantiator`. The installed application list and application search are empty. Static menu commands still work. The stock first-party menu displays applications correctly on the same machine.
This was first reported at https://github.com/DanielLemky/omalaunch/issues/68. I reproduced it on a second machine with the same package versions.
## Reproduction
1. Use Omarchy 4.0.3 and Quickshell 0.3.1.
2. Install and enable Omalaunch v0.4.0. Its manifest declares `"kinds": ["menu", "bar-widget"]`.
3. Open its Apps submenu or search for an installed application.
4. Disable Omalaunch and enable `omarchy.menu` for comparison.
Expected: the third-party menu receives the app-library API promised to plugins with the `menu` kind.
Actual: its injected `PluginShellApi` has the correct plugin ID, but `appLibrary` is null. The stock menu works because it receives the full shell, not this API.
## Confirmed cause
In `shell/shell.qml`:
1. `computePanelEntries()` puts registry manifests in the panel model.
2. `Instantiator` converts the nested `kinds` array to a QML `V4Sequence`.
3. The loader calls `pluginShellFor(panelEntry.manifest)` with that converted value.
4. `manifestHasKind()` requires `Array.isArray(manifest.kinds)`. This returns false for the sequence, although `kinds.indexOf("menu")` returns 0.
5. `createScopedPluginShell()` therefore creates an API without app-library access.
A previous lookup with the original registry manifest can first create a valid menu API. The delegate lookup then changes the capability profile to `no-menu`, which revokes that API and replaces it.
The plugin's separately injected public manifest looks correct because `publicPluginManifest()` copies it through JSON. That converts the sequence back to an array, but it is too late for the capability check.
The following small test reproduces the conversion without a desktop window or Omalaunch. Save it as `shell.qml` and run `QT_QPA_PLATFORM=offscreen quickshell -p shell.qml`:
```qml
import QtQuick
import QtQml.Models
import Quickshell
ShellRoot {
id: root
property var manifest: ({ id: "example.menu", kinds: ["menu"] })
property var entries: [{ manifest: root.manifest }]
Instantiator {
model: root.entries
delegate: QtObject {
required property var modelData
Component.onCompleted: {
var kinds = modelData.manifest.kinds
console.log("delegate", Array.isArray(kinds),
Object.prototype.toString.call(kinds), kinds.indexOf("menu"))
}
}
}
Component.onCompleted: {
console.log("registry", Array.isArray(manifest.kinds))
Qt.callLater(Qt.quit)
}
}
```
Output on Quickshell 0.3.1:
```text
delegate false [object V4Sequence] 0
registry true
```
## Tested correction
Resolve the plugin ID to the registry's validated manifest inside `pluginShellFor()`, before the trust and capability checks. Do not use the delegate's converted manifest for those decisions:
```qml
function pluginShellFor(manifest) {
var key = String(manifest && manifest.id || "")
if (!key) return null
var registeredManifest = shell.pluginRegistry.installedPlugins[key]
if (!registeredManifest) return null
if (registeredManifest.__isFirstParty) return shell
return shell.createScopedPluginShell(registeredManifest, key, true,
shell.pluginHasBarCapabilities(registeredManifest))
}
```
I tested this correction in a separate copy of the packaged 4.0.3 shell, with clean Omalaunch v0.4.0. Installed applications appeared. Search from Apps and from the root menu worked. Selecting Alacritty opened a new Alacritty window. Reopening the menu and rescanning plugins retained application access.
An earlier diagnostic test returned 98 application rows after the type check was corrected. The original path returned zero rows because the library was null.
No packaged files were edited. The standard shell and plugin were restored after testing. Screenshots and a private `omarchy debug --no-sudo --print` log were collected; the complete system log is not included because it contains unrelated machine details.
## Scope
`AppLibrary.qml`, `AppSearch.js`, and the stock menu QML did not change between v4.0.2 and v4.0.3. The relevant change is the new third-party API injection from #9618, included in the 4.0.3 backport #10733.
This is separate from Omalaunch's use of the raw-only `iconIndexChanged` signal. Correcting the app-library grant restores applications without changing Omalaunch. The icon-refresh compatibility change is being handled separately in Omalaunch.
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.