Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
`omarchy update` reports failure when a user-installed AUR package (hyprmoncfg) can't rebuild: read-only Go module cache left in yay build dir
Reported by lavrinovich86 · filed Sep 26, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
omarchy update finished the system upgrade, then failed at "Update AUR packages". The failing package was hyprmoncfg, which I installed myself from the AUR. It went from 1.19.0-1 to 1.19.1-1. makepkg could not remove the old $srcdir:
==> Removing existing $srcdir/ directory...
rm: cannot remove '/home/riebeklis/.cache/yay/hyprmoncfg/src/go-mod/github.com/!make!now!just/[email protected]/LICENSE': Permission denied
... (thousands more lines like this, all under src/go-mod/) ...
==> ERROR: An unknown error has occurred. Exiting...
-> error making: hyprmoncfg-signal: user defined signal 1
-> Failed to install the following packages. Manual intervention is required:
hyprmoncfg - signal: user defined signal 1
Something went wrong during the update!
'/usr/bin/setpriv' terminated by signal TERM.Cause
The hyprmoncfg PKGBUILD builds with GOMODCACHE="${srcdir}/go-mod". Go makes module-cache directories read-only (dr-xr-xr-x), so the previous build leaves src/go-mod/ behind. yay --cleanafter (which omarchy-update-aur-pkgs passes) does not remove it. The next build then fails when makepkg tries to delete $srcdir.
The root fix belongs in the hyprmoncfg PKGBUILD (upstream: crmne/hyprmoncfg). Adding -modcacherw to the go build/go test flags, or running chmod -R u+w "$srcdir/go-mod" before the build, would fix it. I'm reporting it here because of how it shows up in omarchy update.
Omarchy side
omarchy-update-aur-pkgsrunsyay ... || exit 1. One user-installed AUR package that fails to build makes the whole update end with "Something went wrong during the update!", even though the system packages and migrations already finished. It might be worth saying which package failed and that the system update itself succeeded. Another option is to treat AUR failures as a warning.- The red
'/usr/bin/setpriv' terminated by signal TERM.line looks like a crash, but it appears to be the stay-awake inhibitor being stopped during cleanup.
Workaround
chmod -R u+w ~/.cache/yay/hyprmoncfg/src && rm -rf ~/.cache/yay/hyprmoncfg/src
omarchy updateSystem
- Omarchy
4.0.0.r2304.g7b336b1-1, kernel7.2.5-4-omarchy - yay v13.0.1, go 1.27.1
- hyprmoncfg 1.19.0-1 installed from AUR (not an Omarchy default package)
Filed by Claude Opus 5.5 via Claude Code.
View raw text
### What happened `omarchy update` finished the system upgrade, then failed at "Update AUR packages". The failing package was `hyprmoncfg`, which I installed myself from the AUR. It went from 1.19.0-1 to 1.19.1-1. makepkg could not remove the old `$srcdir`: ``` ==> Removing existing $srcdir/ directory... rm: cannot remove '/home/riebeklis/.cache/yay/hyprmoncfg/src/go-mod/github.com/!make!now!just/[email protected]/LICENSE': Permission denied ... (thousands more lines like this, all under src/go-mod/) ... ==> ERROR: An unknown error has occurred. Exiting... -> error making: hyprmoncfg-signal: user defined signal 1 -> Failed to install the following packages. Manual intervention is required: hyprmoncfg - signal: user defined signal 1 Something went wrong during the update! '/usr/bin/setpriv' terminated by signal TERM. ``` ### Cause The hyprmoncfg PKGBUILD builds with `GOMODCACHE="${srcdir}/go-mod"`. Go makes module-cache directories read-only (`dr-xr-xr-x`), so the previous build leaves `src/go-mod/` behind. `yay --cleanafter` (which `omarchy-update-aur-pkgs` passes) does not remove it. The next build then fails when makepkg tries to delete `$srcdir`. The root fix belongs in the hyprmoncfg PKGBUILD (upstream: crmne/hyprmoncfg). Adding `-modcacherw` to the `go build`/`go test` flags, or running `chmod -R u+w "$srcdir/go-mod"` before the build, would fix it. I'm reporting it here because of how it shows up in `omarchy update`. ### Omarchy side - `omarchy-update-aur-pkgs` runs `yay ... || exit 1`. One user-installed AUR package that fails to build makes the whole update end with "Something went wrong during the update!", even though the system packages and migrations already finished. It might be worth saying which package failed and that the system update itself succeeded. Another option is to treat AUR failures as a warning. - The red `'/usr/bin/setpriv' terminated by signal TERM.` line looks like a crash, but it appears to be the stay-awake inhibitor being stopped during cleanup. ### Workaround ``` chmod -R u+w ~/.cache/yay/hyprmoncfg/src && rm -rf ~/.cache/yay/hyprmoncfg/src omarchy update ``` ### System - Omarchy `4.0.0.r2304.g7b336b1-1`, kernel `7.2.5-4-omarchy` - yay v13.0.1, go 1.27.1 - hyprmoncfg 1.19.0-1 installed from AUR (not an Omarchy default package) Filed by Claude Opus 5.5 via Claude Code.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 19:52 UTC