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.
Update migration fails: owe and owe-lockfeed ship duplicate LockFeed files
Reported by nightdevil00 · filed Oct 7, 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
Description
omarchy update reaches migration 1789764927 ("Enable OWE desktop video backgrounds and lock feed"), which runs omarchy-pkg-add owe owe-lockfeed. Pacman aborts the install because both packages contain the same two files:
error: failed to commit transaction (conflicting files)
/usr/lib/qt6/qml/Owe/LockFeed/libowe_lockfeed.so exists in both 'owe' and 'owe-lockfeed'
/usr/lib/qt6/qml/Owe/LockFeed/qmldir exists in both 'owe' and 'owe-lockfeed'The migration fails on every retry while the repository publishes these package versions. Neither package is installed, so this is not a pre-existing local file conflict.
Steps to reproduce
- Run
omarchy updateon Omarchy4.0.0.r6720.g8e02fc8-1. - Allow the update to reach migration
1789764927and proceed with installing the packages. - Pacman aborts because both package archives claim the same LockFeed files; the migration fails and is retried on the next update.
Package versions / verification
owe 0.2.10-1(Omarchy repository; build date Oct 7, 2026)owe-lockfeed 0.2.9-1(Omarchy repository; build date Oct 5, 2026)- Architecture: x86_64
- Omarchy:
4.0.0.r6720.g8e02fc8-1
Inspected both cached package archives with bsdtar -tf; each includes:
usr/lib/qt6/qml/Owe/LockFeed/libowe_lockfeed.sousr/lib/qt6/qml/Owe/LockFeed/qmldir
Expected behavior
The migration should install a package set without overlapping file ownership and continue to its hook/service setup.
This appears related to #13290, but is a distinct failure: these paths are reported as existing in both packages, rather than as unowned files already present on disk. The package contents and migration package list likely need to be brought into alignment.
View raw text
## Description
`omarchy update` reaches migration `1789764927` ("Enable OWE desktop video backgrounds and lock feed"), which runs `omarchy-pkg-add owe owe-lockfeed`. Pacman aborts the install because both packages contain the same two files:
```
error: failed to commit transaction (conflicting files)
/usr/lib/qt6/qml/Owe/LockFeed/libowe_lockfeed.so exists in both 'owe' and 'owe-lockfeed'
/usr/lib/qt6/qml/Owe/LockFeed/qmldir exists in both 'owe' and 'owe-lockfeed'
```
The migration fails on every retry while the repository publishes these package versions. Neither package is installed, so this is not a pre-existing local file conflict.
## Steps to reproduce
1. Run `omarchy update` on Omarchy `4.0.0.r6720.g8e02fc8-1`.
2. Allow the update to reach migration `1789764927` and proceed with installing the packages.
3. Pacman aborts because both package archives claim the same LockFeed files; the migration fails and is retried on the next update.
## Package versions / verification
- `owe 0.2.10-1` (Omarchy repository; build date Oct 7, 2026)
- `owe-lockfeed 0.2.9-1` (Omarchy repository; build date Oct 5, 2026)
- Architecture: x86_64
- Omarchy: `4.0.0.r6720.g8e02fc8-1`
Inspected both cached package archives with `bsdtar -tf`; each includes:
- `usr/lib/qt6/qml/Owe/LockFeed/libowe_lockfeed.so`
- `usr/lib/qt6/qml/Owe/LockFeed/qmldir`
## Expected behavior
The migration should install a package set without overlapping file ownership and continue to its hook/service setup.
This appears related to [#13290](https://github.com/omacom/omarchy/issues/13290), but is a distinct failure: these paths are reported as existing in *both packages*, rather than as unowned files already present on disk. The package contents and migration package list likely need to be brought into alignment.
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 22:22 UTC