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.
plocate does not index $HOME on Btrfs subvolume setups unless PRUNE_BIND_MOUNTS="no"
Reported by rewisch · filed Dec 2, 2025Closed upstream on 2026-07-27 by the merge of PR #6354 (closed by dhh). GitHub close reason: completed.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy 3.2
What's wrong?
On Btrfs systems locate (plocate) fails to index anything in $HOME. Running updatedb completes without errors, but locate returns no results for files inside the user’s home directory.
The cause is that Arch (and Omarchy, inheriting from Arch) ships:
PRUNE_BIND_MOUNTS="yes"in /etc/updatedb.conf
Btrfs subvolumes appear as bind mounts, so updatedb prunes them even though they are real subvolumes.
Setting it to:
PRUNE_BIND_MOUNTS="no"immediately fixes the issue. This might be a bit crude and I'm not sure whether it might have unintended side-effects for some users.
Another solution might be to create a different db for home (see https://discussion.fedoraproject.org/t/mlocate-does-not-find-files-in-home-on-fedora-33-btrfs/75073) ?
I'd be happy to contribute a solution myself, but without a DISTRIBUTORS.md i'm a bit lost at the moment.
View raw text
### System details Omarchy 3.2 ### What's wrong? On Btrfs systems locate (plocate) fails to index anything in $HOME. Running updatedb completes without errors, but locate returns no results for files inside the user’s home directory. The cause is that Arch (and Omarchy, inheriting from Arch) ships: ``` PRUNE_BIND_MOUNTS="yes" ``` in /etc/updatedb.conf Btrfs subvolumes appear as bind mounts, so updatedb prunes them even though they are real subvolumes. Setting it to: ``` PRUNE_BIND_MOUNTS="no" ``` immediately fixes the issue. This might be a bit crude and I'm not sure whether it might have unintended side-effects for some users. Another solution might be to create a different db for home (see https://discussion.fedoraproject.org/t/mlocate-does-not-find-files-in-home-on-fedora-33-btrfs/75073) ? I'd be happy to contribute a solution myself, but without a DISTRIBUTORS.md i'm a bit lost at the moment.
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.
No decision has been recorded yet.