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.
10x slow kernel startup time after 3.1 update
Reported by qdev0 · filed Oct 21, 2025Closed upstream on 2026-07-18. 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
12th Gen Intel(R) Core(TM) i5-12500H, NVIDIA GeForce RTX 3050 Ti Mobile, 16GB
What's wrong?
~ ❯ systemd-analyze
Startup finished in 4.486s (firmware) + 4.775s (loader) + 23.864s (kernel) + 3.872s (userspace) = 36.999s
graphical.target reached after 2.481s in userspace.Kernel normally takes maximum 3-4 seconds. I don't know if it's related to kernel update or omarchy 3.1 update.
View raw text
### System details 12th Gen Intel(R) Core(TM) i5-12500H, NVIDIA GeForce RTX 3050 Ti Mobile, 16GB ### What's wrong? ```sh ~ ❯ systemd-analyze Startup finished in 4.486s (firmware) + 4.775s (loader) + 23.864s (kernel) + 3.872s (userspace) = 36.999s graphical.target reached after 2.481s in userspace. ``` Kernel normally takes maximum 3-4 seconds. I don't know if it's related to kernel update or omarchy 3.1 update.
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.