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.
GCC14 tests running indefinitely after v3.3.0 update
Reported by luis11181 · filed Jan 8, 2026Closed upstream on 2026-01-08 by dhh. 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
System details
AMD Ryzen 7 xxxxG
What's wrong?
Issue: GCC14 tests running indefinitely after v3.3.0 update
In the v3.3.0 update, my system has been stuck running gcc14 tests for several hours with very slow progress.
Suggestions:
Tests should be skipped by default during installation/updates
Additional context:
I was not prompted about running tests during the installation of the new version.
I try to let the install run to avoid getting the wayland hyperland incompatibility errors in case I stop the update, and then be stuck as mention on other issues
<img width="889" height="605" alt="Image" src="https://github.com/user-attachments/assets/4486d60a-06bf-4699-bacd-cf02c1c8c579" />
View raw text
### System details AMD Ryzen 7 xxxxG ### What's wrong? Issue: GCC14 tests running indefinitely after v3.3.0 update In the v3.3.0 update, my system has been stuck running gcc14 tests for several hours with very slow progress. Suggestions: Tests should be skipped by default during installation/updates Additional context: I was not prompted about running tests during the installation of the new version. I try to let the install run to avoid getting the wayland hyperland incompatibility errors in case I stop the update, and then be stuck as mention on other issues <img width="889" height="605" alt="Image" src="https://github.com/user-attachments/assets/4486d60a-06bf-4699-bacd-cf02c1c8c579" />
- 4486d60a-06bf-4699-bacd-cf02c1c8c579
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.