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

Handle the sudo password prompt that appears during the AUR step of omarchy update

omarchyarchendeavouroscachyosdesktoplaptop
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

The mechanism holds. Read /usr/share/omarchy/bin/omarchy-update and omarchy-update-aur-pkgs on 4.0.4-1: the AUR step is exactly yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs with no sudoloop. omarchy-sudo-keepalive exists, but only omarchy-pkg-install and omarchy-pkg-aur-install source it, not the update. PR #13323 was read in full: it merged 2026-09-26 and adds a one-time sudo /usr/bin/true with a sudo -n /usr/bin/true keepalive every 60 s. On quattro, bin/omarchy-update revokes before AUR, and bin/omarchy-update-aur-pkgs passes --sudo <wrapper> --sudoloop=false. The wrapper default/omarchy/sudo-no-update/sudo execs /usr/bin/sudo -N. The latest release is still v4.0.4 (2026-09-15), so 'not yet in a release' holds. yay's cmd_builder.go confirms the sudoloop is sudo -v every 241 s. Omarchy ships only passwd_tries=10 and does not change timestamp_timeout. Two defects in the fix. The post-#13323 advice says 'let the update skip nothing and then run the AUR step yourself', which is garbled. And the sudoers recipe uses a <user> placeholder where $USER works. I also added the interaction with verifypw=any from the sibling record: a passwordless sudo -v writes no timestamp, so with that setting the sudoloop keeps nothing alive. Not exercised: no update or build was run.

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

A longer timestamp_timeout means any process running as you can use sudo without a password for that long, which is exactly the exposure Omarchy's #13323 change avoids for AUR builds. A sudoers drop-in with a syntax error can lock you out of sudo: always run sudo visudo -c before closing the root shell you edited it from.

Symptom

omarchy update asked for the password once at the start, ran for a while, and then stopped again at the AUR step:


Update AUR packages
...
[sudo] password for <user>:

If nobody is at the keyboard (including omarchy update -y), the prompt sits there until sudo gives up, and the AUR package is never installed. With plain yay -Syu-style long builds outside Omarchy the same thing happens: yay builds for twenty minutes, then asks for the password at the install step.

Cause

sudo caches a successful authentication for timestamp_timeout minutes, and the default is 5 (sudoers(5)). A long AUR build easily outlasts that, so the sudo pacman -U yay runs after building finds no valid timestamp and prompts. sudo's own passwd_timeout is also 5 minutes by default, after which the prompt fails and yay reports error making or an install failure.

Omarchy 4.0.4 (the current release as of 2026-10-04): omarchy-update runs plain sudo in each helper with no keepalive, and the AUR step is yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs with no --sudoloop. Any yay setting you saved yourself is honoured.

Omarchy quattro after PR #13323 (merged 2026-09-26, not yet in a release): the update asks once and keeps that timestamp alive with a background sudo -n /usr/bin/true every minute, but it deliberately revokes it before AUR, because PKGBUILDs are third-party code. AUR then runs last with yay --sudo <no-update wrapper> --sudoloop=false, and the wrapper is sudo -N, which never writes a timestamp. So on that code every sudo call yay makes prompts, by design, and a saved sudoloop is overridden.

Fix

Check what happened in the last run:


grep -nE 'Update AUR packages|password for|timed out|error making' /tmp/omarchy-update.log
yay -Qua          # AUR updates still pending

Omarchy 4.0.4 and plain Arch: make yay keep the timestamp alive during builds. --save writes it to ~/.config/yay/config.json, so omarchy update picks it up too:


yay --sudoloop --save

The sudoloop runs sudo -v once at the start (you type the password then) and repeats it in the background every four minutes until yay exits. If your sudo -v prompts even with passwordless sudo, see the record on verifypw. If you set verifypw=any from that record, sudo -v succeeds without authenticating and writes no timestamp, so the sudoloop then keeps nothing alive for a user who is not fully passwordless.

To finish the skipped AUR updates now, run the same command the updater uses, with the loop:


yay -Sua --sudoloop --cleanafter --ignore gcc14,gcc14-libs

Omarchy after PR #13323 reaches a release: the extra prompts during the AUR step are the intended security boundary, and the updater passes --sudoloop=false, which overrides a saved sudoloop. Run omarchy update while you are at the keyboard. If the AUR step was skipped or failed unattended, run the command above yourself afterwards.

Do not raise timestamp_timeout globally to paper over this. If you must, scope it to your user with a validated drop-in:


echo "Defaults:$USER timestamp_timeout=30" | sudo tee /etc/sudoers.d/90-timestamp >/dev/null
sudo chmod 0440 /etc/sudoers.d/90-timestamp
sudo visudo -c

Verify

yay -Qua prints nothing after the next update. The new log has an Update AUR packages section with no password for line after the first prompt (4.0.4 with sudoloop saved). jq .sudoloop ~/.config/yay/config.json prints true.

Sources

aur-sudo-password-prompt-mid-omarchy-update