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-2146GitHub issuePublicDecided· Duplicate

Shell shortcuts (SUPER+SPACE menu etc.) stop working after monitor disconnect/reconnect via KVM until rescanPlugins

Reported by dennisroy · filed Oct 1, 2026 · open at source

Open at source
Decided: Duplicate — decided by agents · verified 3 days ago.
Duplicate ofShell restart after an update leaves overlapping quickshell generations; menu keybind dies silently while IPC still answers R-2159

This defect is tracked under R-2159. This report describes the same defect, so it is folded under it in the inbox.

Earliest report of this defect: R-2146 (filed Oct 1, 2026).

Decided by agents · verified· Oct 8, 2026

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?
AreaPartly in the audited areamenu· 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

Shell shortcuts (SUPER+SPACE menu etc.) stop working after monitor disconnect/reconnect via KVM until rescanPluginsrevision 1 · captured 2026-10-01 15:59 UTC via poll

Summary

After the only monitor disconnects and reconnects (switching a KVM to another machine and back), shell-routed shortcuts such as SUPER+SPACE (omarchy:menu.root) and the other omarchy:* global shortcuts sometimes stop doing anything. Running omarchy-shell shell rescanPlugins makes them work again.

Steps to reproduce

  1. Single-monitor setup connected through a KVM switch.
  2. Switch the KVM to another machine so Hyprland loses all outputs, then switch back.
  3. Press SUPER+SPACE. The menu sometimes doesn't open; other shell shortcuts are dead too.
  4. Run omarchy-shell shell rescanPlugins. Shortcuts work again.

It's intermittent and doesn't happen on every switch. This machine logged 143 "no outputs" events in 7 days.

Expected

Shell shortcuts keep working after outputs go away and come back.

Logs

Each switch-back logs the following from omarchy-shell, followed by a full panel rebuild:

WARN quickshell.hyprland.ipc: Got removal for monitor "FALLBACK" which was not previously tracked.
INFO qt.qpa.wayland: There are no outputs - creating placeholder screen
WARN scene: QML ShellIpc at file:///usr/share/omarchy/shell/plugins/panels/tailscale/Panel.qml[366:3]: Handler was registered but will not be used because another handler is registered for target omarchy.tailscale
WARN scene: QML ShellIpc at file:///usr/share/omarchy/shell/plugins/panels/bluetooth/Panel.qml[640:3]: Handler was registered but will not be used because another handler is registered for target omarchy.bluetooth
... (same for network, monitor, power, audio, weather, system-update, clock, indicators, elsewhen, agents)
WARN: Layershell screen does not correspond to a real screen. Letting the compositor pick.

The duplicate ShellIpc handler warnings suggest that panels get re-instantiated while the old instances (bound to the removed/placeholder screen) are still alive. hyprctl globalshortcuts still lists omarchy:menu.root and the others. Because rescanPlugins (unloadPanels + rescan) fixes it, my guess is that the omarchy.menu panel loader is left with a stale or "opened" item after the output loss, so shell.toggle() hides an invisible panel or opens it nowhere. I haven't confirmed that in the QML.

Workaround

A socket2 listener that runs omarchy-shell -q shell rescanPlugins about 3s after monitoradded.

System

  • Omarchy 4.0.0.r6691.g8b4eae6-1
  • Hyprland 0.56.2, quickshell 0.3.1-1
  • Kernel 7.2.5-4-omarchy
  • CPU: AMD Ryzen AI 9 HX 370, GPU: Radeon 890M (Strix)
  • Monitor: Samsung Odyssey G95SC on DP-1, via KVM
View raw text
## Summary

After the only monitor disconnects and reconnects (switching a KVM to another machine and back), shell-routed shortcuts such as **SUPER+SPACE** (`omarchy:menu.root`) and the other `omarchy:*` global shortcuts sometimes stop doing anything. Running `omarchy-shell shell rescanPlugins` makes them work again.

## Steps to reproduce

1. Single-monitor setup connected through a KVM switch.
2. Switch the KVM to another machine so Hyprland loses all outputs, then switch back.
3. Press SUPER+SPACE. The menu sometimes doesn't open; other shell shortcuts are dead too.
4. Run `omarchy-shell shell rescanPlugins`. Shortcuts work again.

It's intermittent and doesn't happen on every switch. This machine logged 143 "no outputs" events in 7 days.

## Expected

Shell shortcuts keep working after outputs go away and come back.

## Logs

Each switch-back logs the following from `omarchy-shell`, followed by a full panel rebuild:

```
WARN quickshell.hyprland.ipc: Got removal for monitor "FALLBACK" which was not previously tracked.
INFO qt.qpa.wayland: There are no outputs - creating placeholder screen
WARN scene: QML ShellIpc at file:///usr/share/omarchy/shell/plugins/panels/tailscale/Panel.qml[366:3]: Handler was registered but will not be used because another handler is registered for target omarchy.tailscale
WARN scene: QML ShellIpc at file:///usr/share/omarchy/shell/plugins/panels/bluetooth/Panel.qml[640:3]: Handler was registered but will not be used because another handler is registered for target omarchy.bluetooth
... (same for network, monitor, power, audio, weather, system-update, clock, indicators, elsewhen, agents)
WARN: Layershell screen does not correspond to a real screen. Letting the compositor pick.
```

The duplicate `ShellIpc` handler warnings suggest that panels get re-instantiated while the old instances (bound to the removed/placeholder screen) are still alive. `hyprctl globalshortcuts` still lists `omarchy:menu.root` and the others. Because `rescanPlugins` (`unloadPanels` + rescan) fixes it, my guess is that the `omarchy.menu` panel loader is left with a stale or "opened" item after the output loss, so `shell.toggle()` hides an invisible panel or opens it nowhere. I haven't confirmed that in the QML.

## Workaround

A socket2 listener that runs `omarchy-shell -q shell rescanPlugins` about 3s after `monitoradded`.

## System

- Omarchy 4.0.0.r6691.g8b4eae6-1
- Hyprland 0.56.2, quickshell 0.3.1-1
- Kernel 7.2.5-4-omarchy
- CPU: AMD Ryzen AI 9 HX 370, GPU: Radeon 890M (Strix)
- Monitor: Samsung Odyssey G95SC on DP-1, via KVM

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

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.

  • DuplicateR-2159Decided by agents · verified · 2026-10-08 23:46 UTC