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.
Lock screen fails: WlSessionLock.surface does not create WlSessionLockSurface
Reported by WalidBabi · filed Sep 2, 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?
- 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 (lock) — decided by agents · verified; not a duplicate of another report — decided by agents · verified; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
Description
The pre-suspend lock screen always fails with:
WARN: WlSessionLock.surface does not create a WlSessionLockSurface. Aborting lock.This leaves the session unlocked when the system suspends (lid close, idle timeout, etc.), because the 12s inhibitor budget always expires without securing the session.
Root Cause
In /usr/share/omarchy/shell/plugins/lock/Service.qml (lines 264-288), a Loader is placed as a child of WlSessionLock:
WlSessionLock {
id: sessionLock
locked: false
// ...
Loader {
active: sessionLock.locked || sessionLock.secure
sourceComponent: Component {
WlSessionLockSurface { ... }
}
}
}WlSessionLock declares surface as its default property (Q_CLASSINFO("DefaultProperty", "surface")) with type QQmlComponent*. The Loader (a QQuickItem) gets assigned to this property instead of a proper Component.
When Quickshell's C++ code calls mSurfaceComponent->create() and then qobject_cast<WlSessionLockSurface*>, the cast fails because a Loader is not a WlSessionLockSurface.
Fix
Replace the Loader with a bare Component:
WlSessionLock {
id: sessionLock
locked: false
// ...
Component {
WlSessionLockSurface { ... }
}
}WlSessionLock manages surface lifecycle internally — it calls create() per-screen when locked is set to true. No Loader wrapper is needed.
Environment
- Omarchy: 4.0.1-1
- Quickshell: 0.3.1-1
- Hyprland: 0.56.2-1
- Kernel: 7.1.9-arch1-2
Workaround
Clone the lock plugin and apply the fix locally:
omarchy plugin clone omarchy.lock
# Edit ~/.config/omarchy/plugins/<user>.lock/Service.qml
# Replace the Loader block with a bare ComponentView raw text
## Description
The pre-suspend lock screen always fails with:
```
WARN: WlSessionLock.surface does not create a WlSessionLockSurface. Aborting lock.
```
This leaves the session unlocked when the system suspends (lid close, idle timeout, etc.), because the 12s inhibitor budget always expires without securing the session.
## Root Cause
In `/usr/share/omarchy/shell/plugins/lock/Service.qml` (lines 264-288), a `Loader` is placed as a child of `WlSessionLock`:
```qml
WlSessionLock {
id: sessionLock
locked: false
// ...
Loader {
active: sessionLock.locked || sessionLock.secure
sourceComponent: Component {
WlSessionLockSurface { ... }
}
}
}
```
`WlSessionLock` declares `surface` as its default property (`Q_CLASSINFO("DefaultProperty", "surface")`) with type `QQmlComponent*`. The `Loader` (a `QQuickItem`) gets assigned to this property instead of a proper `Component`.
When Quickshell's C++ code calls `mSurfaceComponent->create()` and then `qobject_cast<WlSessionLockSurface*>`, the cast fails because a Loader is not a WlSessionLockSurface.
## Fix
Replace the `Loader` with a bare `Component`:
```qml
WlSessionLock {
id: sessionLock
locked: false
// ...
Component {
WlSessionLockSurface { ... }
}
}
```
`WlSessionLock` manages surface lifecycle internally — it calls `create()` per-screen when `locked` is set to true. No Loader wrapper is needed.
## Environment
- Omarchy: 4.0.1-1
- Quickshell: 0.3.1-1
- Hyprland: 0.56.2-1
- Kernel: 7.1.9-arch1-2
## Workaround
Clone the lock plugin and apply the fix locally:
```bash
omarchy plugin clone omarchy.lock
# Edit ~/.config/omarchy/plugins/<user>.lock/Service.qml
# Replace the Loader block with a bare Component
```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.
- Decided by agents · verified: in the audited area (lock)
- Decided by agents · verified: not a duplicate of another report
- Decided by agents · verified: matches no known issue
The outcome (valid, duplicate, not a bug, …) is not decided yet.