Proof Portal

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-472GitHub issuePublicReceived

App list/launcher disappeared after kernel update

Reported by rafi-the-dev · filed Sep 16, 2026 · open at source

In the audited area (menu) — decided by agents · verified. Not validated yet.

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?
AreaIn 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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: in the audited area (menu) — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

App list/launcher disappeared after kernel updaterevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Environment: - Omarchy Version: 4.0.4-1 - Kernel: 7.2.5-3-omarchy - Hardware: ASUS TUF Gaming F17 (i7-13620H, RTX 4070 Mobile) - WM/DE: Hyprland 0.56.2 / Wayland - OS: Omarchy (Arch-based) - Memory: 32GB RAM

What's wrong?

Description:
After updating the system and switching to a new kernel, all applications disappeared from the Omarchy menu/app
list. The .desktop files were still present in ~/.local/share/applications and /usr/share/applications, but the
menu was empty.

Steps to Reproduce:
1. Perform a system update that includes a kernel change.
2. Reboot into the new kernel.
3. Open the Omarchy application menu.
4. Observe that no applications are listed.

Environment:
- Omarchy Version: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- Hardware: ASUS TUF Gaming F17 (i7-13620H, RTX 4070 Mobile)
- WM/DE: Hyprland 0.56.2 / Wayland
- OS: Omarchy (Arch-based)
- Memory: 32GB RAM

Resolution:
The issue was resolved by running:
omarchy refresh shell && omarchy refresh applications && omarchy restart shell

This suggests that the shell configuration or application indexing may need to be reconciled after certain
system-level updates.

View raw text
### System details

 Environment:  - Omarchy Version: 4.0.4-1  - Kernel: 7.2.5-3-omarchy  - Hardware: ASUS TUF Gaming F17 (i7-13620H, RTX 4070 Mobile)  - WM/DE: Hyprland 0.56.2 / Wayland  - OS: Omarchy (Arch-based)  - Memory: 32GB RAM

### What's wrong?

Description:
 After updating the system and switching to a new kernel, all applications disappeared from the Omarchy menu/app
 list. The .desktop files were still present in ~/.local/share/applications and /usr/share/applications, but the
 menu was empty.

 Steps to Reproduce:
 1. Perform a system update that includes a kernel change.
 2. Reboot into the new kernel.
 3. Open the Omarchy application menu.
 4. Observe that no applications are listed.

 Environment:
 - Omarchy Version: 4.0.4-1
 - Kernel: 7.2.5-3-omarchy
 - Hardware: ASUS TUF Gaming F17 (i7-13620H, RTX 4070 Mobile)
 - WM/DE: Hyprland 0.56.2 / Wayland
 - OS: Omarchy (Arch-based)
 - Memory: 32GB RAM

 Resolution:
 The issue was resolved by running:
 omarchy refresh shell && omarchy refresh applications && omarchy restart shell

 This suggests that the shell configuration or application indexing may need to be reconciled after certain
 system-level updates.

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.

  • Decided by agents · verified: in the audited area (menu)

The outcome (valid, duplicate, not a bug, …) is not decided yet.