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.
OMARCHY VERY SLOW AND LAGGY AFTER LAST 2-3 UPDATES ALSO CLIPBOARD HISTORY IS NOT WORKING
Reported by isbafatima90-arch · filed May 8, 2026Closed upstream on 2026-05-08. 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
OMARCHY 3.8.0
What's Wrong?
This is a serious performance regression that is actively driving users away from Omarchy.
Do NOT dismiss this as a hardware issue — Omarchy was butter smooth on versions 3.0.4 / 3.0.5 on this exact same hardware. This is an unambiguous, reproducible regression introduced somewhere in the last few updates. The specs have not changed. The machine has not changed. Omarchy has changed — and not for the better.
The current state of 3.8.0 is:
- Painfully slow — response times that were once instant now feel sluggish and unacceptable
- Horrifying to use — the UX has gone from delightful to repulsive; every interaction is a reminder that something is deeply broken
- Completely broken clipboard support — Super + C does not copy in About. A basic, fundamental shortcut. Non-functional. How did this ship?
This is not a fringe edge case. This is the core experience. Every user on 3.8.0 is suffering through this right now. Every day this goes unfixed is another user who gives up and leaves.
You had something great in 3.0.4. You broke it. Please fix it — urgently.
See attached screenshot for reference.
<img width="875" height="600" alt="Image" src="https://github.com/user-attachments/assets/d3d6a5b5-2e10-41b6-aa8d-9f7c7b9a99f2" />
View raw text
### System Details OMARCHY 3.8.0 ### What's Wrong? **This is a serious performance regression that is actively driving users away from Omarchy.** Do NOT dismiss this as a hardware issue — Omarchy was **butter smooth** on versions **3.0.4 / 3.0.5** on this **exact same hardware**. This is an unambiguous, reproducible regression introduced somewhere in the last few updates. The specs have not changed. The machine has not changed. **Omarchy has changed — and not for the better.** The current state of 3.8.0 is: - **Painfully slow** — response times that were once instant now feel sluggish and unacceptable - **Horrifying to use** — the UX has gone from delightful to repulsive; every interaction is a reminder that something is deeply broken - **Completely broken clipboard support** — `Super + C` does not copy in About. A basic, fundamental shortcut. Non-functional. How did this ship? This is not a fringe edge case. This is the core experience. **Every user on 3.8.0 is suffering through this right now.** Every day this goes unfixed is another user who gives up and leaves. You had something great in 3.0.4. You broke it. **Please fix it — urgently.** --- *See attached screenshot for reference.* <img width="875" height="600" alt="Image" src="https://github.com/user-attachments/assets/d3d6a5b5-2e10-41b6-aa8d-9f7c7b9a99f2" />
- d3d6a5b5-2e10-41b6-aa8d-9f7c7b9a99f2
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.