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

Chromium launch OSD remains visible after browser opens

Reported by goutham794 · filed Sep 13, 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

Chromium launch OSD remains visible after browser opensrevision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

After launching Chromium, the small “Launching Chromium…” overlay remains on screen indefinitely. Chromium itself opens successfully.

Expected behavior

The launch overlay should disappear when the application opens, or when the launch timeout expires.

Observed sequence

  1. Launch Chromium (the session journal records gtk-launch chromium.desktop).
  2. The “Launching Chromium…” overlay appears.
  3. Chromium opens, but the overlay remains for several minutes.

Observed once; repeatability and the exact launcher interaction have not been established.

System details

  • Omarchy: 4.0.3-1
  • Quickshell: 0.3.1-1
  • Hyprland: 0.56.2-2
  • Chromium: 152.0.7977.82-1
  • CPU: Intel Core i7-1165G7
  • GPUs: Intel Iris Xe Graphics and NVIDIA GeForce MX450
  • Two displays: eDP-1 (1280×720 logical), HDMI-A-1 (1920×1080 logical)

Diagnostics

Live Hyprland inspection confirmed a mapped, visible native Wayland Chromium window on HDMI-A-1 while the omarchy-osd overlay remained on eDP-1, owned by the Omarchy shell process.

The session journal records Chromium launching at 17:16:19 on September 13, 2026. The inspected journal excerpt contained no AppLibrary exception explaining the failure.

In the installed shell/services/AppLibrary.qml, launch feedback appears after 2 seconds with duration: 0. closeLaunchFeedback() invokes omarchy-shell osd close, and a 15-second timer is intended to invoke that cleanup. This suggests investigating the launch feedback cleanup/IPC path; the underlying cause has not been established.

omarchy debug --no-sudo --print is unavailable in this installation (returns “Unknown Omarchy command”).

Screenshot

A cropped screenshot shows the persistent “Launching Chromium…” overlay.

<img width="379" height="114" alt="Image" src="https://github.com/user-attachments/assets/aad5d8fd-8ead-4232-86d4-4d550d8152a7" />

View raw text
## What happened

After launching Chromium, the small “Launching Chromium…” overlay remains on screen indefinitely. Chromium itself opens successfully.

## Expected behavior

The launch overlay should disappear when the application opens, or when the launch timeout expires.

## Observed sequence

1. Launch Chromium (the session journal records `gtk-launch chromium.desktop`).
2. The “Launching Chromium…” overlay appears.
3. Chromium opens, but the overlay remains for several minutes.

Observed once; repeatability and the exact launcher interaction have not been established.

## System details

- Omarchy: 4.0.3-1
- Quickshell: 0.3.1-1
- Hyprland: 0.56.2-2
- Chromium: 152.0.7977.82-1
- CPU: Intel Core i7-1165G7
- GPUs: Intel Iris Xe Graphics and NVIDIA GeForce MX450
- Two displays: eDP-1 (1280×720 logical), HDMI-A-1 (1920×1080 logical)

## Diagnostics

Live Hyprland inspection confirmed a mapped, visible native Wayland Chromium window on HDMI-A-1 while the `omarchy-osd` overlay remained on eDP-1, owned by the Omarchy shell process.

The session journal records Chromium launching at 17:16:19 on September 13, 2026. The inspected journal excerpt contained no AppLibrary exception explaining the failure.

In the installed `shell/services/AppLibrary.qml`, launch feedback appears after 2 seconds with `duration: 0`. `closeLaunchFeedback()` invokes `omarchy-shell osd close`, and a 15-second timer is intended to invoke that cleanup. This suggests investigating the launch feedback cleanup/IPC path; the underlying cause has not been established.

`omarchy debug --no-sudo --print` is unavailable in this installation (returns “Unknown Omarchy command”).

## Screenshot

A cropped screenshot shows the persistent “Launching Chromium…” overlay. 

<img width="379" height="114" alt="Image" src="https://github.com/user-attachments/assets/aad5d8fd-8ead-4232-86d4-4d550d8152a7" />
  • aad5d8fd-8ead-4232-86d4-4d550d8152a7

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 12:49 UTC