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.
Yay error after upgrading to Omarchy 3.2.3
Reported by Carson-Bay · filed Dec 16, 2025Closed upstream on 2025-12-16 by dhh, as a duplicate of #3877 (R-3882). GitHub close reason: duplicate.
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.3, AMD Ryzen 7 5700x, Nvidia RTX 4060
What's wrong?
At the end of update to 3.2.3, Yay gave an error: yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory
Checking about, it seems like Omarchy was successful in upgrading to 3.2.3, but now any command using yay has the exact same error.
View raw text
### System details Omarchy 3.2.3, AMD Ryzen 7 5700x, Nvidia RTX 4060 ### What's wrong? At the end of update to 3.2.3, Yay gave an error: `yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory` Checking about, it seems like Omarchy was successful in upgrading to 3.2.3, but now any command using yay has the exact same error.
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.