How to Update Omarchy Safely

Update Omarchy and Arch Linux with backup, snapshot, release-note, change-record, reboot, and recovery safeguards.

Rolling updates are not inherently bad, but they do not belong just before a meeting, during travel, or when no recovery time is available. A reliable update has preparation, execution, verification, and recovery stages.

Check the v4.0.4 kernel update

v4.0.4 makes linux-omarchy the default boot kernel. Reboot after updating and inspect uname -r and pacman -Q linux-omarchy separately, then test webcam, audio, network, suspend, and displays. Official improvement claims are not independent benchmarks by this guide. See kernel verification.

Before updating

Save work and push or back up projects;
confirm the latest user-data backup succeeded and open a sample;
read current Omarchy update notes and important Arch Linux news;
maintain stable power and networking;
reserve time for reboot and recovery.

A snapshot is not a data backup

A system snapshot can roll back system state, but may disappear with the same failed disk. Important files still need independent media or remote backup.

Run the update

The graphical path is Super + Space → Update → Omarchy. The terminal entry point is:

omarchy update

This creates a pre-update snapshot, installs current Omarchy, runs migrations, and updates packages from the official mirror plus installed AUR packages. Do not run a general Arch updater, AUR helper, or custom update script at the same time. Read replacement, conflict, and reboot prompts; do not answer yes automatically.

Record the time and before/after version. On failure, preserve complete output and distinguish download, signature/key, file conflict, package script, and free-space errors. They require different remedies.

The four update channels

Channel	Purpose	Risk
stable	Daily-use default, following releases and a delayed validated mirror	Lowest
RC	Final validation before a major release	Medium-high
edge	Development builds and faster Arch packages	High
dev	A local source checkout for Omarchy development	Highest

Switch through Update → Channel or the current official terminal entry point:

omarchy-channel-set

It opens an interactive channel selection; read it before confirming. Normal users should remain on stable. Before RC, edge, or dev, prove that Limine snapshots and an independent backup are reachable.

Do not bypass Omarchy with a direct pacman -Syu or yay -Syu. The integrated update combines a pre-update snapshot, migrations, default configuration, and system/AUR packages.

Firmware updates

Use Super + Space → Update → Firmware. On first use Omarchy installs fwupd, then checks LVFS firmware for BIOS, SSDs, docks, and other hardware. Some firmware is written only during reboot. Connect AC power and never interrupt a firmware write.

Verify after updating

Confirm the update exits normally, capture a diagnostic baseline, and perform a planned reboot:

omarchy debug
systemctl reboot

Then test:

login and disk unlock;
networking, DNS, and VPN;
displays, audio, and input;
critical browser, terminal, and editor workflows;
custom themes and shortcuts.

A visible desktop alone is not proof. A small test of the workflow you depend on is more useful.

When to roll back

If boot, data access, or core work is affected and evidence ties it to the update, follow current official snapshot or recovery guidance to return to a known state. Record the failing package and symptom so the next update is not a blind repeat.

For one broken application, narrow scope with the troubleshooting guide before restoring the whole system.

See snapshots and system recovery for the complete recovery path. Sources: Omarchy Updates, System Snapshots, and Arch Linux News.