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

Handle 'removing X breaks dependency Y required by Z'

archomarchyendeavouroscachyosmanjarodesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Thread 295233 has the exact krunner5 output, loqs's pacman -Syu krunner and Lone_Wolf's TTY pacman -Rdd krunner5 then pacman -Syu. Thread 254564 shows the 'breaks dependency ... required by' refusal. Confirmed locally on 4.0.4-1: pacman -Qi omarchy depends on hyprland, quickshell, uwsm, sddm, limine, limine-mkinitcpio-hook, limine-snapper-sync, snapper, pipewire, wireplumber and pacman-contrib (so pactree is present). omarchy-menu.jsonc has a 'Remove' menu, and omarchy-remove-* commands exist in /usr/share/omarchy/bin. The ALPM guard refuses -S plus -u unless OMARCHY_ALLOW_DIRECT_PACMAN=1, so the Omarchy branches are right. The defect is in the danger field. It covers -Rdd but not pacman -Rsc, which the fix offers before the Omarchy branch. Cascade removal of any core component (snapper, limine, hyprland and so on) removes the omarchy package itself, and with it /usr/share/omarchy and everything that requires it. Here that includes flea-bin, which pacman -Qi omarchy lists under Required By. The danger is corrected to cover it. Nothing was removed.

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

pacman -Rsc removes every package that depends on the target, recursively. On Omarchy 4, if the target is one of Omarchy's core components (pacman -Qi omarchy lists them), that includes the omarchy package itself, which takes /usr/share/omarchy and every Omarchy command with it. Always run pacman -Rsc --print <package> first and stop if omarchy or omarchy-settings is in the list. pacman -Rdd removes a package while other installed packages still depend on it. Until the upgrade that follows completes, those dependents can fail to start. Run both commands back to back from a TTY. On Omarchy 4, never follow -Rdd with a bare sudo pacman -Syu: the update guard refuses it and leaves the system with the package removed and nothing upgraded.

Symptom

Uninstalling something is refused:


$ sudo pacman -Rs krunner5
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing krunner5 breaks dependency 'krunner' required by akonadi-search
:: removing krunner5 breaks dependency 'krunner5' required by milou

On Omarchy 4 it can name Omarchy itself, for example :: removing snapper breaks dependency 'snapper' required by omarchy. It also turns up mid-upgrade, when a package dropped from the repositories has to go before the upgrade can continue.

Cause

pacman will not remove a package that another installed package declares as a dependency, because the dependent would break. -s only removes dependencies nobody else needs. It never removes the packages that depend on your target. On Omarchy 4 the omarchy package itself depends on its core components (hyprland, quickshell, uwsm, sddm, limine, limine-mkinitcpio-hook, limine-snapper-sync, snapper, pipewire, wireplumber and more, see pacman -Qi omarchy), so removing one of those means removing Omarchy. In the upgrade case, an old package left behind by a repository split still satisfies something, and its replacement is not yet installed.

Fix

See who needs the package:


pacman -Qi <package> | grep 'Required By'
pactree -r <package>            # full reverse tree, from pacman-contrib

**You want the dependents gone too.** Preview, then remove the package and everything that depends on it. Read the list before confirming:


pacman -Rsc --print <package>
sudo pacman -Rsc <package>

**The dependent is omarchy (Omarchy 4).** Stop. That component is part of the system. Use Omarchy's own remover for optional software (Super + Space > Remove, or the omarchy-remove-* commands) and leave the core packages installed.

**Mid-upgrade, an obsolete package blocks it.** Install the replacement in the same full upgrade so the old one can be replaced:


sudo pacman -Syu krunner                                       # plain Arch
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu krunner      # Omarchy 4, then run: omarchy update

Only as a last resort, from a TTY rather than the desktop, remove the single obsolete package ignoring dependencies and upgrade immediately. Plain Arch:


sudo pacman -Rdd krunner5
sudo pacman -Syu

Omarchy 4, where a direct pacman -Syu is refused by the update guard:


sudo pacman -Rdd krunner5
omarchy update

Verify

pacman -Dk reports no missing dependencies after the change.

Sources

removing-package-breaks-dependency