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-1012GitHub issuePublicDecided· Out of scope

Launching a single-instance app hidden on the scratchpad does not reveal it

Reported by JoNil · filed Sep 3, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Launching a single-instance app hidden on the scratchpad does not reveal itrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

AMD Ryzen 9 9950X, NVIDIA GeForce RTX 5090, Omarchy 4.0.2-1, Hyprland 0.56.2, kernel 7.1.9-arch1-2. Obsidian 1.13.7-2 (Electron 43.4.1).

What's wrong?

Launching an already-running single-instance application does not make it visible when its only window is on the hidden scratchpad. The launch appears to do nothing even though the application is healthy and running.

Steps to reproduce

  1. Launch Obsidian.
  2. Focus its window and press SUPER + ALT + S to move it to special:scratchpad.
  3. Press SUPER + S so the scratchpad is hidden.
  4. Launch Obsidian again from the Omarchy application launcher.

Actual behavior

No Obsidian window becomes visible. Obsidian remains running with exactly one mapped Hyprland client on workspace special:scratchpad, while every monitor reports no visible special workspace. Repeated launcher attempts invoke gtk-launch obsidian.desktop, but Obsidian's single-instance behavior leaves the existing window on the hidden scratchpad.

This was diagnosed from the live state rather than inferred from a crash: there was no Obsidian coredump, the existing process had remained active, and hyprctl clients -j showed its sole window on special:scratchpad.

Expected behavior

When a single-instance application is launched again and its existing window is on a hidden special workspace, Omarchy should reveal that special workspace on the current monitor and focus the existing window. This should work for Obsidian and other single-window/single-instance applications.

The current behavior is especially confusing because it looks identical to a failed launch. SUPER + S reveals the supposedly missing window immediately.

View raw text
### System details

AMD Ryzen 9 9950X, NVIDIA GeForce RTX 5090, Omarchy 4.0.2-1, Hyprland 0.56.2, kernel 7.1.9-arch1-2. Obsidian 1.13.7-2 (Electron 43.4.1).

### What's wrong?

Launching an already-running single-instance application does not make it visible when its only window is on the hidden scratchpad. The launch appears to do nothing even though the application is healthy and running.

#### Steps to reproduce

1. Launch Obsidian.
2. Focus its window and press `SUPER + ALT + S` to move it to `special:scratchpad`.
3. Press `SUPER + S` so the scratchpad is hidden.
4. Launch Obsidian again from the Omarchy application launcher.

#### Actual behavior

No Obsidian window becomes visible. Obsidian remains running with exactly one mapped Hyprland client on workspace `special:scratchpad`, while every monitor reports no visible special workspace. Repeated launcher attempts invoke `gtk-launch obsidian.desktop`, but Obsidian's single-instance behavior leaves the existing window on the hidden scratchpad.

This was diagnosed from the live state rather than inferred from a crash: there was no Obsidian coredump, the existing process had remained active, and `hyprctl clients -j` showed its sole window on `special:scratchpad`.

#### Expected behavior

When a single-instance application is launched again and its existing window is on a hidden special workspace, Omarchy should reveal that special workspace on the current monitor and focus the existing window. This should work for Obsidian and other single-window/single-instance applications.

The current behavior is especially confusing because it looks identical to a failed launch. `SUPER + S` reveals the supposedly missing window immediately.

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

  • Related PRpr/8570· confirmed

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 10:41 UTC