Fix the Walker launcher stuck on "Waiting for elephant"
Checked on this Omarchy 4.0.2-1 workstation that Walker is not part of Omarchy 4 at all: pacman -Q walker and pacman -Q elephant both fail, pacman -Ql omarchy lists no walker or elephant path, and the only matches for either word under /usr/share/omarchy are unrelated English prose, a code comment about a TOML walker in shell/Commons/Color.qml line 173, a comment in shell/plugins/agents/Panel.qml line 415, and the elephant emoji in shell/plugins/emojis/emojis.json. SUPER + SPACE is bound to omarchy-menu toggle in /usr/share/omarchy/default/hypr/bindings/utilities.lua line 1, and omarchy-restart-walker is not among the 428 scripts in /usr/share/omarchy/bin. Against upstream, the quattro tree of omacom/omarchy contains no path matching walker or elephant, while the Omarchy 3 master tree contains bin/omarchy-restart-walker, bin/omarchy-launch-walker, default/walker/, default/elephant/ and install/config/walker-elephant.sh, so this is an Omarchy 3 record that the corpus was presenting as an Omarchy record. The cited issue 2638 is real and does support the symptom, filed against Omarchy v3.1.1 with the exact placeholder text, and dhh closed it with "Closing because Quattro replaces Walker, Elephant, and the old menu surfaces with the native Omarchy shell launcher and menus." I did not reject the record because the problem is still reachable rather than impossible: walker 2.17.0-1 and elephant 2.22.0-1 are current in the AUR, upstream released both on 2026-07-16, and the string Waiting for elephant... still exists verbatim in the Walker v2.17.0 tarball at resources/themes/default/layout.xml line 64, so an Omarchy 4 user who installed Walker by hand can hit exactly this. One command in the old fix was wrong rather than merely stale: there is no walker.service, because the Walker v2.17.0 tarball ships no systemd unit and Omarchy 3's own bin/omarchy-restart-walker restarts app-walker@autostart.service, the unit generated from walker.desktop. Elephant does ship assets/elephant.service, so the elephant half of the old fix was correct. I confirmed omarchy upgrade to quattro is the right invocation from the omarchy:examples metadata line in /usr/share/omarchy/bin/omarchy-upgrade-to-quattro, so that command is kept unchanged, and I added the elephant-desktopapplications provider case that the issue thread reports as the fix for the empty-list variant. I lowered frequency from common to rare because the distribution no longer ships the component, leaving only users who added Walker themselves. Not exercised: I installed nothing and did not reproduce either failure, and applies_to still lists omarchy unqualified alongside omarchy-3, which should be narrowed by hand since the verdict schema has no field for it. I replaced the basecamp/omarchy issue URL with the canonical omacom/omarchy one, which is the same issue, because the search API does not follow the rename.
omarchy upgrade to quattro is a major version migration that rewrites config files and can clobber customizations. See the shell-json-reset-by-quattro-upgrade record before running it.
Symptom
Pressing SUPER + SPACE opens the Walker launcher, but the search box shows the placeholder Launch... with a transparent list below it reading Waiting for elephant.... Nothing is searchable. A near variant is a launcher that opens and lists nothing at all, which means Elephant is running but has no provider installed. coredumpctl may show Process <pid> (walker) of user 1000 dumped core with a stack through g_application_run and libglib-2.0.
This is an Omarchy 3 symptom. Omarchy 3 shipped Walker and Elephant, Omarchy 4 (Quattro) does not install either package, and on Omarchy 4 SUPER + SPACE opens the Quickshell menu instead. An Omarchy 4 machine can only show this if Walker was installed from the AUR by hand.
Cause
Walker's backend indexer (elephant) is not running or has crashed, so Walker has nothing to query and leaves its placeholder row on screen. The string comes from Walker's own default theme, resources/themes/default/layout.xml, so it is Walker reporting the backend missing rather than Omarchy reporting anything. It happens intermittently after an update that restarts the two services at the wrong moment, and sometimes Walker itself segfaults inside its GLib main loop and takes the pairing down with it. A separate cause produces an empty list rather than the placeholder: Elephant's data providers are packaged separately from Elephant, so a running Elephant with no elephant-desktopapplications installed indexes nothing.
Omarchy 4 replaced the whole pairing with the native Quickshell launcher in /usr/share/omarchy/shell, and SUPER + SPACE is bound to omarchy-menu toggle. Neither walker nor elephant is installed and no omarchy-restart-walker exists. Walker and Elephant are still maintained upstream and are current in the AUR, so the failure remains reachable on Omarchy 4 for anyone who added them themselves.
Fix
First establish which Omarchy you are on, because the two cases have different fixes:
pacman -Q omarchy walker elephant
If walker and elephant both report was not found, skip to the Omarchy 4 section.
**On Omarchy 3**, restart the launcher and its backend:
omarchy-restart-walker
That script restarts elephant.service and app-walker@autostart.service. If it does not take, drive the two units directly. Note the Walker unit is app-walker@autostart.service, which systemd-xdg-autostart-generator derives from ~/.config/autostart/walker.desktop. There is no walker.service:
systemctl --user restart elephant.service
systemctl --user restart app-walker@autostart.service
systemctl --user status elephant.service
Watch the failure live while reproducing it:
journalctl --user -f
# then press SUPER + SPACE
If the launcher opens but lists nothing instead of showing Waiting for elephant..., Elephant is running and has no provider. Providers are separate AUR packages:
yay -S elephant-desktopapplications
If it recurs constantly, check for crashes:
coredumpctl list walker
**On Omarchy 4 (Quattro)** there is nothing to restart. The launcher is the Quickshell shell in /usr/share/omarchy/shell, SUPER + SPACE runs omarchy-menu toggle, and no Walker or Elephant package is installed:
grep -rn 'SUPER + SPACE' /usr/share/omarchy/default/hypr/bindings/utilities.lua
If you see this symptom on Omarchy 4 you installed Walker from the AUR yourself and it is yours to manage. Elephant ships its own unit at assets/elephant.service, so systemctl --user restart elephant.service still applies, but Omarchy will not start Walker for you and omarchy-restart-walker does not exist.
**Migrating from Omarchy 3 removes the component entirely:**
omarchy upgrade to quattro
Verify
On Omarchy 3, SUPER + SPACE shows your applications immediately with no Waiting for elephant... line, systemctl --user is-active elephant.service prints active, and systemctl --user is-active app-walker@autostart.service prints active.
On Omarchy 4, SUPER + SPACE opens the Quickshell menu and pacman -Q walker reports error: package 'walker' was not found. That absence is the expected state, not a fault.