OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
hyprland-config medium common DISPUTE

Fix SUPER+Space and the Omarchy menu stopping after a game or Discord

omarchyhyprlandarch
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The diagnosis is sound and the cited issues (#2089, #2558) are real Omarchy 3.x reports: the bind survives while the exec'd launcher process dies, so Hyprland reports nothing because exec succeeded from its point of view. hyprctl binds is a documented info command and is the right first check. But the recovery half is obsolete and one claim is fabricated. I listed all 440 scripts in basecamp/omarchy bin/. There is no omarchy-refresh-walker, and no walker-related script of any kind. A repo-wide code search returns walker only in bin/omarchy-upgrade-to-quattro (i.e. the migration away from it). Omarchy 4.x replaced Walker with omarchy-shell / omarchy-menu. So omarchy-refresh-walker returns 'command not found' because it no longer exists, not because of a capitalised O. That explanation is invented and will send a user chasing a typo that isn't there. yay -S walker is also wrong for the era it targets: Omarchy 3.x installed the AUR binary package, walker-bin.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

omarchy-refresh-hyprland overwrites every user Hyprland config in ~/.config/hypr with the shipped defaults. It backs each one up as <file>.bak.<epoch> first, but your customisations will not be in the active file afterwards.

Symptom

SUPER+Space (the app launcher) and the Omarchy menu randomly stop responding after a while, often after opening a game or Discord. Other keybindings still work. Only a reboot seems to fix it.

Cause

The keybinding itself is fine. The launcher process it execs has died or wedged. In Omarchy 3.x this was Walker (/usr/bin/walker --gapplication-service) crashing or losing its D-Bus service. Hyprland reports nothing because exec succeeded from its point of view.

Fix

First confirm the bind is still registered. The record is right that this is the useful discriminator:


hyprctl binds | grep -B2 -A4 -i 'SPACE'

Then fix by Omarchy generation.

Omarchy 4.x (current): Walker is gone, and the launcher is the Omarchy shell. Restart it rather than rebooting:


omarchy-restart-shell

If the bindings themselves look wrong, restore the shipped ones (backs yours up as *.bak.<epoch>):


omarchy-refresh-hyprland
hyprctl reload

Omarchy 3.x (historical), where the launcher was Walker:


pkill walker
walker --gapplication-service &
# if the binary is genuinely missing, the AUR package is walker-bin, not walker:
yay -S walker-bin

There is no omarchy-refresh-walker in current Omarchy (verified against all 440 scripts in bin/). If you get 'command not found', the script has been removed, not miscapitalised.

Verify

hyprctl binds | grep SPACE shows the bind, and pressing SUPER+Space opens the launcher without a reboot.

Sources

omarchy-super-space-launcher-stops-working