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.
Increase default memlock hard/soft limits
Reported by clwalker85 · filed Nov 2, 2025Closed upstream on 2026-02-02. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
What do you need?
Is this something that can get a reasonable default in Omarchy installations? See this tweet for more information:
https://x.com/rpcs3/status/1330818231527944194
If you use RPCS3 on Linux, you may want to increase the memlock hard/soft limits to unlimited on /etc/security/limits.conf in order to avoid potential crashes or freezes.
The default value is unfortunately archaic - only 64KB - which doesn't allow us to properly do memory locks.
<img width="528" height="258" alt="Image" src="https://github.com/user-attachments/assets/c841eb67-b1ad-4e7e-9f4f-7020411330b4" />
View raw text
### What do you need? Is this something that can get a reasonable default in Omarchy installations? See this tweet for more information: https://x.com/rpcs3/status/1330818231527944194 If you use RPCS3 on Linux, you may want to increase the memlock hard/soft limits to unlimited on /etc/security/limits.conf in order to avoid potential crashes or freezes. The default value is unfortunately archaic - only 64KB - which doesn't allow us to properly do memory locks. <img width="528" height="258" alt="Image" src="https://github.com/user-attachments/assets/c841eb67-b1ad-4e7e-9f4f-7020411330b4" />
- c841eb67-b1ad-4e7e-9f4f-7020411330b4
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.