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.
Apps lauched via keybinding is slow and stuttery compared to the app lauched via waker
Reported by abhiram-ar · filed Feb 5, 2026Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
Omarchy 3.3.3, AMD Ryzen 9 4900HS (16) @ 3.00 GHz, 4.63 GiB / 15.04 GiB (31%)
What's wrong?
I launched the Obsidian app that comes preinstalled with omarchy via SUPER+Shift+O. When I try to open the command palette of Obsidian, it has a stuttered animation.
I launched the same Obsidian app via the Walker GUI, and when I try to do the same, everything is smooth.
Obsidian launched via keybinding
https://github.com/user-attachments/assets/61bd1bf0-0cac-4dd8-9ff1-f584690b98ac
Obsidian launched via Walker
https://github.com/user-attachments/assets/4a1e9431-7d03-4de0-917d-1619c30430dd
As a matter of fact. I have noticed the app launching itself is slow when using the keybinding compared to the GUI approaches throughout Omarchy. Alacritty startup time has a noticeable difference when launched via keybinding (SUPER+Enter) and right-clicking on the system profiler in the waybar.
update:
In .config/hypr/binding.conf, Why are we disabling gpu by default
bindd = SUPER SHIFT, O, Obsidian, exec, omarchy-launch-or-focus ^obsidian$ "uwsm-app -- obsidian -disable-gpu --enable-wayland-ime"getting rid of the --disable-gpu flag seems to fix the problem
bindd = SUPER SHIFT, O, Obsidian, exec, omarchy-launch-or-focus ^obsidian$ "uwsm-app -- obsidian --enable-wayland-ime"View raw text
### System details Omarchy 3.3.3, AMD Ryzen 9 4900HS (16) @ 3.00 GHz, 4.63 GiB / 15.04 GiB (31%) ### What's wrong? I launched the Obsidian app that comes preinstalled with omarchy via `SUPER+Shift+O`. When I try to open the command palette of Obsidian, it has a stuttered animation. I launched the same Obsidian app via the Walker GUI, and when I try to do the same, everything is smooth. ### Obsidian launched via keybinding https://github.com/user-attachments/assets/61bd1bf0-0cac-4dd8-9ff1-f584690b98ac ### Obsidian launched via Walker https://github.com/user-attachments/assets/4a1e9431-7d03-4de0-917d-1619c30430dd As a matter of fact. I have noticed the app launching itself is slow when using the keybinding compared to the GUI approaches throughout Omarchy. Alacritty startup time has a noticeable difference when launched via keybinding (SUPER+Enter) and right-clicking on the system profiler in the waybar. update: In `.config/hypr/binding.conf`, Why are we disabling gpu by default ```bash bindd = SUPER SHIFT, O, Obsidian, exec, omarchy-launch-or-focus ^obsidian$ "uwsm-app -- obsidian -disable-gpu --enable-wayland-ime" ``` getting rid of the `--disable-gpu` flag seems to fix the problem ```bash bindd = SUPER SHIFT, O, Obsidian, exec, omarchy-launch-or-focus ^obsidian$ "uwsm-app -- obsidian --enable-wayland-ime" ```
- 61bd1bf0-0cac-4dd8-9ff1-f584690b98ac
- 4a1e9431-7d03-4de0-917d-1619c30430dd
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.