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-pkg-aur-install hangs after transaction: foreground updatedb scans FUSE/network mounts
Reported by dekritpn · filed Oct 10, 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
System details
Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, FUSE Mount:** Remote cloud storage mounted under $HOME, plocate 1.1.25-1
What's wrong?
Description
AUR package installation via omarchy pkg aur install hangs indefinitely (or takes tens of minutes) after package transaction completes, seemingly stuck at:
(3/3) Updating the desktop file MIME type cache...
Root Cause
1. omarchy-pkg-aur-install calls sudo updatedb --prune-bind-mounts=no --add-prunepaths=/.snapshots in the foreground after yay finishes. Because updatedb outputs nothing, it appears as though the last pacman hook (update-desktop-database) has hung.
2. Because --prune-bind-mounts=no allows plocate to scan Btrfs /@home, any user who has a FUSE network/cloud mount (such as rclone mount with filesystem type fuse.rclone) will have their entire remote cloud storage recursively traversed over the network during every AUR install.
Proposed Solutions
1. Remove or background `updatedb` in `omarchy-pkg-aur-install`:
omarchy-pkg-install does not run updatedb. If indexing is desired, it should either run in the background (... &) or be left to the daily plocate-updatedb.timer.
2. Add common FUSE types to PRUNEFS:
Include --add-prunefs "fuse.rclone fuse.gvfsd-fuse fuse.portal" in Omarchy's plocate service override (/usr/lib/systemd/system/plocate-updatedb.service.d/10-omarchy.conf) and/or installer defaults for /etc/updatedb.conf.
View raw text
### System details
Omarchy 4.0.4-1, kernel 7.2.5-3-omarchy, FUSE Mount:** Remote cloud storage mounted under `$HOME`, plocate 1.1.25-1
### What's wrong?
Description
AUR package installation via `omarchy pkg aur install` hangs indefinitely (or takes tens of minutes) after package transaction completes, seemingly stuck at:
`(3/3) Updating the desktop file MIME type cache...`
Root Cause
1. `omarchy-pkg-aur-install` calls `sudo updatedb --prune-bind-mounts=no --add-prunepaths=/.snapshots` in the foreground after `yay` finishes. Because `updatedb` outputs nothing, it appears as though the last pacman hook (`update-desktop-database`) has hung.
2. Because `--prune-bind-mounts=no` allows `plocate` to scan Btrfs `/@home`, any user who has a FUSE network/cloud mount (such as `rclone mount` with filesystem type `fuse.rclone`) will have their entire remote cloud storage recursively traversed over the network during every AUR install.
Proposed Solutions
1. **Remove or background `updatedb` in `omarchy-pkg-aur-install`:**
`omarchy-pkg-install` does not run `updatedb`. If indexing is desired, it should either run in the background (`... &`) or be left to the daily `plocate-updatedb.timer`.
2. **Add common FUSE types to PRUNEFS:**
Include `--add-prunefs "fuse.rclone fuse.gvfsd-fuse fuse.portal"` in Omarchy's `plocate` service override (`/usr/lib/systemd/system/plocate-updatedb.service.d/10-omarchy.conf`) and/or installer defaults for `/etc/updatedb.conf`.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
- Fixed bypr/14914· confirmed
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-10 17:10 UTC