Proof Portal

Sign in
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-4812GitHub issuePublicReceived

Power panel (SUPER+CTRL+P) does not open: QML binding loop in Panel.qml

Reported by nojaf · filed Sep 1, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7119 (R-1772). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked 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?
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

Power panel (SUPER+CTRL+P) does not open: QML binding loop in Panel.qmlrevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

Pressing the default keybind SUPER + CTRL + P (bound to omarchy-shell shell toggle omarchy.power) does nothing visible, the power panel never appears.

Running the underlying command manually also produces no visible panel:

omarchy-shell shell toggle omarchy.power

The Quickshell process log shows a QML binding loop at the moment of toggling:

WARN scene: QML Panel at file:///usr/share/omarchy/shell/plugins/panels/power/Panel.qml[9:1]: Binding loop detected for property "opened":

Expected

The power panel (shutdown/reboot/logout/suspend menu) should open.

Steps to reproduce

  1. Fresh Omarchy 4.0.2-1 install/session.
  2. Press SUPER + CTRL + P (or run omarchy-shell shell toggle omarchy.power directly).
  3. Nothing opens. Check journalctl --user _PID=<quickshell pid> around that moment, see the binding-loop warning on Panel.qml[9:1] for the opened property.

Workaround

The older menu still works fine: omarchy-menu toggle system (same command as the XF86PowerOff binding), so I rebound SUPER + CTRL + P to that locally.

System details

  • Omarchy version: 4.0.2-1
  • Hyprland: 0.56.2 (v0.56.2, commit efb50993780079460b0cbed1363e2166a2de1d9f)
  • Kernel: 7.1.9-arch1-2
  • CPU: 12th Gen Intel(R) Core(TM) i7-12700K
  • GPU: NVIDIA GeForce RTX 3070 (GA104)
View raw text
## What happened

Pressing the default keybind `SUPER + CTRL + P` (bound to `omarchy-shell shell toggle omarchy.power`) does nothing visible, the power panel never appears.

Running the underlying command manually also produces no visible panel:
```
omarchy-shell shell toggle omarchy.power
```

The Quickshell process log shows a QML binding loop at the moment of toggling:
```
WARN scene: QML Panel at file:///usr/share/omarchy/shell/plugins/panels/power/Panel.qml[9:1]: Binding loop detected for property "opened":
```

## Expected

The power panel (shutdown/reboot/logout/suspend menu) should open.

## Steps to reproduce

1. Fresh Omarchy 4.0.2-1 install/session.
2. Press `SUPER + CTRL + P` (or run `omarchy-shell shell toggle omarchy.power` directly).
3. Nothing opens. Check `journalctl --user _PID=<quickshell pid>` around that moment, see the binding-loop warning on `Panel.qml[9:1]` for the `opened` property.

## Workaround

The older menu still works fine: `omarchy-menu toggle system` (same command as the `XF86PowerOff` binding), so I rebound `SUPER + CTRL + P` to that locally.

## System details

- Omarchy version: 4.0.2-1
- Hyprland: 0.56.2 (v0.56.2, commit efb50993780079460b0cbed1363e2166a2de1d9f)
- Kernel: 7.1.9-arch1-2
- CPU: 12th Gen Intel(R) Core(TM) i7-12700K
- GPU: NVIDIA GeForce RTX 3070 (GA104)

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.