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.
Bar drag-reorder moves wrong instance for widgets with allowMultiple (matches by module id, first wins)
Reported by BriamLeyton · filed Sep 9, 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
Description
In the Quickshell bar, drag-reordering a bar widget that has allowMultiple: true in its manifest always moves the first instance with that module id, not the slot the user is dragging.
Expected behavior
Dropping a dragged slot moves that slot's layout entry.
Actual behavior
Dropping moves the entry of the first instance of the same module id anywhere on the bar. With multiple instances, the wrong widget teleports to the drop position and the dragged one never moves.
Steps to reproduce
- Install a plugin with
allowMultiple: true(e.g. a spacer widget), and place two instances of it on the bar. - Drag the second instance to a new position and drop it.
- Instead of the second instance, the first instance moves to the drop position.
Root cause
Bar.qml's dropBarModule() → moveModuleInConfig(config, source.region, source.moduleName, toRegion, beforeName) identifies the source by module name (rawEntryIndex(entries, moduleName)), which returns the first entry whose id matches. The drag source is a slot that already knows its exact entry (region + index), but only the name survives into the move.
Suggested fix: pass the source entry's index (or a stable per-instance uid) alongside the name, and locate the source entry by it.
Notes
Found while building a small multi-instance plugin; any widget with multiple simultaneous instances hits this. Also affects cross-section drags for the same reason.
- Omarchy 4.0.3-1, Arch Linux, Hyprland + Quickshell
- Filed by GLM (Z.ai) via pi coding agent.
View raw text
### Description In the Quickshell bar, drag-reordering a bar widget that has `allowMultiple: true` in its manifest always moves the **first** instance with that module id, not the slot the user is dragging. ### Expected behavior Dropping a dragged slot moves that slot's layout entry. ### Actual behavior Dropping moves the entry of the first instance of the same module id anywhere on the bar. With multiple instances, the wrong widget teleports to the drop position and the dragged one never moves. ### Steps to reproduce 1. Install a plugin with `allowMultiple: true` (e.g. a spacer widget), and place two instances of it on the bar. 2. Drag the **second** instance to a new position and drop it. 3. Instead of the second instance, the **first** instance moves to the drop position. ### Root cause `Bar.qml`'s `dropBarModule()` → `moveModuleInConfig(config, source.region, source.moduleName, toRegion, beforeName)` identifies the source by **module name** (`rawEntryIndex(entries, moduleName)`), which returns the first entry whose `id` matches. The drag source is a slot that already knows its exact entry (region + index), but only the name survives into the move. Suggested fix: pass the source entry's index (or a stable per-instance uid) alongside the name, and locate the source entry by it. ### Notes Found while building a small multi-instance plugin; any widget with multiple simultaneous instances hits this. Also affects cross-section drags for the same reason. --- - Omarchy 4.0.3-1, Arch Linux, Hyprland + Quickshell - Filed by GLM (Z.ai) via pi coding agent.
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 11:15 UTC