Stop iwd, systemd-networkd and NetworkManager from fighting over the same interface
The cause and the one-manager rule hold: the Arch wiki NetworkManager page says each interface should be managed by one DHCP client or network manager and, under the iwd backend, 'Do not enable iwd.service'. BBS #273965 shows the exact iwd SEGV restart loop on an archinstall system with NetworkManager, iwd and systemd-networkd all enabled. On this 4.0.4-1 workstation (networkmanager 1.58.1-1) iwd is not installed, systemd-networkd is disabled and wpa_supplicant.service is disabled but active through D-Bus activation, as the cause says. The fix is wrong in one important place. I tested systemctl --root=<scratch> disable iwd.service dhcpcd.service wpa_supplicant.service with systemd 261: each missing unit prints 'Failed to disable unit: Unit iwd.service does not exist' and the command exits 1. Reading systemctl-enable.c (v258), the D-Bus path returns on that error before the --now stop, so on any machine missing one of the listed units (every Omarchy install lacks dhcpcd) nothing is stopped and the conflicting daemon keeps running until reboot. The record calls that message harmless. A masked unit is ignored with exit 0, which I also tested, so systemd-networkd-wait-online.service (masked on Omarchy) is fine. Second, disable --now wpa_supplicant.service stops the supplicant that NetworkManager itself is using (its unit carries BusName=fi.w1.wpa_supplicant1 and the D-Bus service file names it as SystemdService), which drops Wi-Fi for no gain. The conflicting supplicant is a per-interface wpa_supplicant@ instance. The fix now disables only units that are actually loaded, one at a time, and targets wpa_supplicant@ instances. The verify step also ignored NetworkManager-dispatcher.service, which is enabled on stock Omarchy. Nothing was disabled or stopped on this machine.
Disabling the service that currently holds your connection drops the network immediately. Over SSH you lose the session and may not get it back. Do it at the console, and enable NetworkManager in the same step.
Symptom
Wi-Fi connects, drops, reconnects, and keeps cycling for minutes before it settles. Or the interface gets two addresses, or nmcli says the device is unmanaged or unavailable while something else is clearly configuring it. The journal can show iwd.service: Main process exited, code=dumped, status=11/SEGV with a climbing restart counter, or both systemd-networkd and NetworkManager handing out leases on the same link. This is common right after an archinstall install that enabled several network services.
Cause
Each interface must be managed by exactly one network manager or DHCP client. archinstall and copy-pasted guides often leave several enabled at once: iwd.service, wpa_supplicant.service, systemd-networkd, dhcpcd and NetworkManager. They race for association and DHCP on the same device. When NetworkManager uses iwd as its Wi-Fi backend, iwd.service must still not be enabled on its own, because NetworkManager starts iwd itself. Omarchy 4 ships NetworkManager with wpa_supplicant and enables nothing else. On this workstation systemd-networkd is disabled, iwd is not installed and wpa_supplicant.service is disabled (NetworkManager D-Bus-activates it). So the conflict appears on Omarchy only when a user adds a second manager.
Fix
See what is enabled and running:
systemctl list-unit-files --state=enabled | grep -E 'NetworkManager|iwd|wpa_supplicant|systemd-networkd|dhcpcd|connman|netctl'
systemctl --type=service --state=running | grep -E 'NetworkManager|iwd|wpa_supplicant|networkd|dhcpcd|connman'
Keep NetworkManager and disable the rest. Do this from a local console, because the network drops. Disable each unit on its own and skip the ones that are not installed. systemctl disable --now a b c fails as a whole when any one of the listed units does not exist, and then it stops nothing:
for unit in iwd.service dhcpcd.service connman.service \
systemd-networkd.service systemd-networkd.socket systemd-networkd-wait-online.service; do
if [[ $(systemctl show -P LoadState "$unit") == loaded ]]; then
sudo systemctl disable --now "$unit"
fi
done
# per-interface supplicants started outside NetworkManager, e.g. wpa_supplicant@wlan0
for unit in $(systemctl list-units --all --plain --no-legend 'wpa_supplicant@*' 'wpa_supplicant-nl80211@*' | awk '{print $1}'); do
sudo systemctl disable --now "$unit"
done
sudo systemctl enable --now NetworkManager.service
Leave wpa_supplicant.service alone. NetworkManager starts it through D-Bus and uses it for Wi-Fi, so stopping it drops the connection you are keeping. It is disabled on a stock Omarchy 4 install and still shows as running, which is correct.
If you deliberately run NetworkManager with the iwd backend (wifi.backend=iwd in /etc/NetworkManager/conf.d/), keep the iwd package installed but leave iwd.service disabled, because NetworkManager starts iwd itself. On Omarchy 4, do not set the iwd backend: iwd is not installed (see nm-wifi-backend-iwd-orphaned-after-quattro).
The reverse choice (iwd plus systemd-networkd, no NetworkManager) is also valid on plain Arch. The rule is one manager per interface, not which one.
Verify
systemctl list-unit-files --state=enabled | grep -E 'iwd|dhcpcd|connman|systemd-networkd|wpa_supplicant@' prints nothing, and NetworkManager.service is enabled (NetworkManager-dispatcher.service is its helper and stays enabled). nmcli device shows the interfaces as connected and not unmanaged. journalctl -b -u iwd is empty after a reboot, and the connection stays up.