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 centre section is unclickable with an absolute pointing device; relative mouse mode fixes it
Reported by novastate · filed Aug 28, 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
Note: This bug was investigated and this report written by Claude Code and submitted on my behalf.
Summary
Every clickable widget in the bar's centre section is unresponsive when the
pointer is an absolute pointing device. The left and right sections work
normally at the same time. Switching the remote client from absolute to
relative mouse mode makes the centre section work immediately.
Affected in the centre: omarchy.clock, omarchy.weather, omarchy.microphone,omarchy.media. (omarchy.indicators and omarchy.system-update have no click
handling, and omarchy.keyboard-layout hides itself with a single layout.)
Environment
- Omarchy 4.0.1-1, Hyprland 0.56.2
- KVM guest, Radeon RX 580 passed through, single output
HDMI-A-13840x2160 @scale = 1.25 - Accessed over Sunshine/Moonlight. Hyprland sees
mouse-passthrough (absolute),
mouse-passthrough, qemu-qemu-usb-tablet, virtualps/2-vmware-vmmouse
- Default bar.centerAnchor: "omarchy.clock", otherwise stock bar config
Steps to reproduce
- Drive the session with an absolute pointing device (Moonlight in its normal,
non-game mouse mode).
2. Left-click omarchy.clock in the centre section. Nothing happens — no calendar.
Right-click and middle-click do nothing either.
3. Left-click any widget in the left or right section. Works normally.
4. Switch Moonlight to game mode (relative mouse). Click the clock again — the
calendar opens.
Moving a widget between sections tracks the behaviour exactly: a third-party
bar widget worked in the right section, stopped working when moved to the
centre, and worked again when moved back.
Evidence that the widget itself is fine
A synthetic click delivered through uinput at the clock's exact position
opens the calendar, while a real click at the same coordinates does not:
ydotool mousemove --absolute -x 768 -y 6 # lands on 1536,12 = the clock
ydotool click 0xC0
# -> omarchy-keyboard-panel layer appears in `hyprctl layers`(An open bar panel shows up as the layer omarchy-keyboard-panel, which makes
this measurable without looking at the screen.)
Evidence that the pointer reports position continuously
Both hyprctl dispatch movecursor 1536 13 and ydotool mousemove --absolute
are overridden within a fraction of a second — hyprctl cursorpos snaps back to
wherever the physical pointer is, even when the mouse is not being moved. The
injected position only holds while the user keeps completely still.
Candidate mechanism (not proven)
Two independent drag gestures in plugins/bar/Bar.qml share the same threshold,dragThreshold: Style.space(4) — roughly 2 px per axis, and this display isscale = 1.25:
CenterGestureArea.onPositionChanged(Bar.qml:1426) →startDrag(), and
onReleased (Bar.qml:1440) sets suppressClick = true
- ModuleSlot.modulePointer.onPositionChanged (Bar.qml:1682) → module reorder drag
A pointer that streams absolute positions during a press can cross a 4-unit
threshold without the user moving the mouse, turning every click into a drag.
What this does not explain: why only the centre section is affected.ModuleSlot is used by all three sections, and per #8111 CenterGestureArea isanchors.fill: parent inside CenterModules { anchors.fill: parent }, so it
spans the entire bar rather than just the centre. CenterGestureArea also hasacceptedButtons: Qt.LeftButton, so it should not affect the right-click that
is also dead. I could not close that gap and did not want to guess in a report.
Expected
Bar widgets are clickable regardless of whether the pointer is absolute or relative.
Related
- #8111 — tray icons unclickable, clicks falling through to the bar gesture area
- #6881 — press-and-hold on a centre widget leaking the bar-move ghost (closed)
Possibly the same family of problem: pointer input on the bar being consumed by
drag gestures rather than reaching widgets.
Workaround
Run the remote client in relative (game) mouse mode, or keep clickable widgets
out of the centre section.
View raw text
> **Note:** This bug was investigated and this report written by [Claude Code](https://claude.com/claude-code) and submitted on my behalf.
## Summary
Every clickable widget in the bar's **centre section** is unresponsive when the
pointer is an absolute pointing device. The left and right sections work
normally at the same time. Switching the remote client from absolute to
relative mouse mode makes the centre section work immediately.
Affected in the centre: `omarchy.clock`, `omarchy.weather`, `omarchy.microphone`,
`omarchy.media`. (`omarchy.indicators` and `omarchy.system-update` have no click
handling, and `omarchy.keyboard-layout` hides itself with a single layout.)
## Environment
- Omarchy 4.0.1-1, Hyprland 0.56.2
- KVM guest, Radeon RX 580 passed through, single output `HDMI-A-1` 3840x2160 @ `scale = 1.25`
- Accessed over Sunshine/Moonlight. Hyprland sees `mouse-passthrough (absolute)`,
`mouse-passthrough`, `qemu-qemu-usb-tablet`, `virtualps/2-vmware-vmmouse`
- Default `bar.centerAnchor: "omarchy.clock"`, otherwise stock bar config
## Steps to reproduce
1. Drive the session with an absolute pointing device (Moonlight in its normal,
non-game mouse mode).
2. Left-click `omarchy.clock` in the centre section. Nothing happens — no calendar.
Right-click and middle-click do nothing either.
3. Left-click any widget in the left or right section. Works normally.
4. Switch Moonlight to game mode (relative mouse). Click the clock again — the
calendar opens.
Moving a widget between sections tracks the behaviour exactly: a third-party
bar widget worked in the right section, stopped working when moved to the
centre, and worked again when moved back.
## Evidence that the widget itself is fine
A synthetic click delivered through `uinput` at the clock's exact position
opens the calendar, while a real click at the same coordinates does not:
```
ydotool mousemove --absolute -x 768 -y 6 # lands on 1536,12 = the clock
ydotool click 0xC0
# -> omarchy-keyboard-panel layer appears in `hyprctl layers`
```
(An open bar panel shows up as the layer `omarchy-keyboard-panel`, which makes
this measurable without looking at the screen.)
## Evidence that the pointer reports position continuously
Both `hyprctl dispatch movecursor 1536 13` and `ydotool mousemove --absolute`
are overridden within a fraction of a second — `hyprctl cursorpos` snaps back to
wherever the physical pointer is, even when the mouse is not being moved. The
injected position only holds while the user keeps completely still.
## Candidate mechanism (not proven)
Two independent drag gestures in `plugins/bar/Bar.qml` share the same threshold,
`dragThreshold: Style.space(4)` — roughly 2 px per axis, and this display is
`scale = 1.25`:
- `CenterGestureArea.onPositionChanged` (Bar.qml:1426) → `startDrag()`, and
`onReleased` (Bar.qml:1440) sets `suppressClick = true`
- `ModuleSlot.modulePointer.onPositionChanged` (Bar.qml:1682) → module reorder drag
A pointer that streams absolute positions during a press can cross a 4-unit
threshold without the user moving the mouse, turning every click into a drag.
**What this does not explain:** why only the centre section is affected.
`ModuleSlot` is used by all three sections, and per #8111 `CenterGestureArea` is
`anchors.fill: parent` inside `CenterModules { anchors.fill: parent }`, so it
spans the entire bar rather than just the centre. `CenterGestureArea` also has
`acceptedButtons: Qt.LeftButton`, so it should not affect the right-click that
is also dead. I could not close that gap and did not want to guess in a report.
## Expected
Bar widgets are clickable regardless of whether the pointer is absolute or relative.
## Related
- #8111 — tray icons unclickable, clicks falling through to the bar gesture area
- #6881 — press-and-hold on a centre widget leaking the bar-move ghost (closed)
Possibly the same family of problem: pointer input on the bar being consumed by
drag gestures rather than reaching widgets.
## Workaround
Run the remote client in relative (game) mouse mode, or keep clickable widgets
out of the centre section.
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 09:49 UTC