OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core medium very-common DISPUTE

Repair the menu and keybindings after updating with pacman instead of omarchy

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

The underlying advice (always update through Omarchy) is correct and manual/30-updates.md warns about it. But three things are wrong for current Omarchy. (1) The symptom is largely obsolete: bin/omarchy-update-pacman-guard is an ALPM pre-transaction hook that ABORTS any direct -S+-u transaction with a 'Woah partner...' message, so users can no longer silently drift this way. (2) The cause is obsolete: Omarchy 4 is installed as pacman packages (omarchy, omarchy-settings) at /usr/share/omarchy, not a git checkout at ~/.local/share/omarchy. Migrations live in /usr/share/omarchy/migrations with state in ~/.local/state/omarchy/migrations. (3) Menu keybind is Super+Space, not Super+Alt+Space. Also, omarchy-refresh-hyprland is presented as a harmless repair but it OVERWRITES every user hypr config (monitors, bindings, input, looknfeel, autostart) with defaults. That needs a warning.

The cause above was rewritten on 2026-08-30 to match this note; the fix was corrected by the audit itself.
RISK

omarchy-refresh-hyprland OVERWRITES ~/.config/hypr/{hyprland,autostart,bindings,input,looknfeel,monitors}.conf with stock defaults. Back them up first: cp -r ~/.config/hypr ~/.config/hypr.bak.

Symptom

User updates with sudo pacman -Syu or yay -Syu out of habit. Packages update fine, but afterwards the Omarchy menu has missing/renamed entries, keybindings from the release notes don't exist, themes look wrong, or the top bar shows an "emergency mode" banner. Re-running pacman -Syu says everything is up to date.

Cause

Omarchy 4 is installed as pacman packages (omarchy, omarchy-settings) at /usr/share/omarchy, and ships numbered migration scripts in /usr/share/omarchy/migrations with applied-state in ~/.local/state/omarchy/migrations. omarchy update runs those migrations after the package upgrade. A bare pacman -Syu / yay -Syu upgrades packages and never runs them, so config and packages drift apart. On current Omarchy this is largely prevented rather than merely warned about: bin/omarchy-update-pacman-guard is an ALPM pre-transaction hook that aborts any direct -S + -u transaction.

Fix

Always update through Omarchy so migrations and config updates run alongside packages:


omarchy update

or from the menu: Super + Space > **Update** > **Omarchy**.

Note that on current Omarchy you generally cannot cause this drift any more. A direct pacman -Syu / yay -Syu is stopped by Omarchy's ALPM guard, which prints a message pointing you back at omarchy update. If you deliberately bypassed it with OMARCHY_ALLOW_DIRECT_PACMAN=1, just run the update once and pending migrations replay in order:


omarchy update

Check what is actually still pending before assuming config is the problem:


omarchy-migrate --pending

Only if the Hyprland configs are genuinely mangled, reset them, but be aware this is destructive:


# WARNING: overwrites ~/.config/hypr/{hyprland,monitors,input,bindings,looknfeel,autostart}.lua
# with Omarchy defaults. Timestamped .bak copies are left beside each file.
omarchy-refresh-hyprland

To reset a single file instead of all of them:


omarchy-refresh-config hypr/bindings.lua

(Menu equivalent: **Update** > **Config**.)

Verify

omarchy update reports no pending migrations on a second run, and the new keybindings/menu entries from the release notes are present.

Sources

pacman-syu-instead-of-omarchy-update