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.
Screensaver only dismisses on keyboard input, not mouse movement
Reported by gurupak · filed Aug 28, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7762 (R-1580). 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
Omarchy version: 4.0.1-1
What happened:
Once the screensaver (omarchy-launch-screensaver) starts, moving the mouse
does not dismiss it. Only a keypress dismisses it.
Expected:
Per the script's own comment, mouse input should also dismiss the screensaver.
Root cause (verified in source):
/usr/share/omarchy/bin/omarchy-screensaver has:
# Exit the screensaver on signals and input from keyboard and mouse
...
while pgrep -t "${tty#/dev/}" -x ttfx >/dev/null; do
if read -n1 -t 1 || ! screensaver_in_focus; then
exit_screensaver
fi
done
read -n1 -t 1 only reads bytes arriving on the terminal's stdin, which is
what a keypress produces. Plain mouse movement never appears on stdin because
the script never enables terminal mouse-tracking (no \e[?1000h), so the
terminal emulator has no reason to forward mouse events at all. The other
check, screensaver_in_focus, only fires if a different window becomes
focused, which plain mouse movement over the fullscreen screensaver window
does not do either.
Separately, the Quickshell idle service
(/usr/share/omarchy/shell/plugins/services/idle/Service.qml,
handleActiveSignal()) deliberately ignores the compositor's idle-monitor
"active" signal once the screensaver window is open, and waits specifically
for the screensaver window to close (a Hyprland closewindow event) — so even
compositor-level mouse-activity detection doesn't reach the dismiss logic.
Steps to reproduce:
1. Let the screensaver's idle timeout elapse (idle.screensaver in shell.json).
2. Once the screensaver terminal window appears, move the mouse without
pressing any key.
3. Screensaver stays up indefinitely; only a keypress dismisses it.
Suggested fix:
Enable terminal mouse-tracking mode in omarchy-screensaver (e.g. printf
'\e[?1003h' on start / '\e[?1003l' on exit) and read mouse-motion escape
sequences in the read loop, or otherwise have the launching side listen for
raw pointer motion (e.g. via the compositor) instead of relying on terminal
stdin.
View raw text
**Omarchy version:** 4.0.1-1
**What happened:**
Once the screensaver (omarchy-launch-screensaver) starts, moving the mouse
does not dismiss it. Only a keypress dismisses it.
**Expected:**
Per the script's own comment, mouse input should also dismiss the screensaver.
**Root cause (verified in source):**
/usr/share/omarchy/bin/omarchy-screensaver has:
# Exit the screensaver on signals and input from keyboard and mouse
...
while pgrep -t "${tty#/dev/}" -x ttfx >/dev/null; do
if read -n1 -t 1 || ! screensaver_in_focus; then
exit_screensaver
fi
done
`read -n1 -t 1` only reads bytes arriving on the terminal's stdin, which is
what a keypress produces. Plain mouse movement never appears on stdin because
the script never enables terminal mouse-tracking (no `\e[?1000h`), so the
terminal emulator has no reason to forward mouse events at all. The other
check, `screensaver_in_focus`, only fires if a different window becomes
focused, which plain mouse movement over the fullscreen screensaver window
does not do either.
Separately, the Quickshell idle service
(/usr/share/omarchy/shell/plugins/services/idle/Service.qml,
handleActiveSignal()) deliberately ignores the compositor's idle-monitor
"active" signal once the screensaver window is open, and waits specifically
for the screensaver window to close (a Hyprland closewindow event) — so even
compositor-level mouse-activity detection doesn't reach the dismiss logic.
**Steps to reproduce:**
1. Let the screensaver's idle timeout elapse (idle.screensaver in shell.json).
2. Once the screensaver terminal window appears, move the mouse without
pressing any key.
3. Screensaver stays up indefinitely; only a keypress dismisses it.
**Suggested fix:**
Enable terminal mouse-tracking mode in omarchy-screensaver (e.g. printf
'\e[?1003h' on start / '\e[?1003l' on exit) and read mouse-motion escape
sequences in the read loop, or otherwise have the launching side listen for
raw pointer motion (e.g. via the compositor) instead of relying on terminal
stdin.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.