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.
Applications including Chromium, Brave and Electron apps hang on paste: wl-clip-persist appears to be the culprit
Reported by mlabbe · filed Sep 22, 2025Closed upstream on 2025-10-26 by ryanrhughes. 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, Dell XPS 9560
What's wrong?
In the default install of Omarchy, wl-clip-persist is entrusted to receive (on copy) and send (on paste) clipboard data to applications. wl-clip-persist 0.4.3 (the latest) appears to have a condition wherein it does not complete the paste, causing the paste-receiving app to hang indefinitely. There are two workarounds:
- Short term: From any un-hung app, copy something to the clipboard. This un-hangs the app.
- Disable
wl-clip-persistby commenting out the relevant line in ~/.local/share/omarchy/default/hypr/autostart.conf and logging back in (but of course you lose the benefits).
Since the bug is in the upstream application, I reported it in full detail with repro steps here:
https://github.com/Linus789/wl-clip-persist/issues/22
My investigation was performed using Emacs with PGTK. This is the version of Emacs that Omarchy ships under the Install->Editor->Emacs window. However, as stated in that bug, I believe the issue lies in wl-clip-persist because of the subtleties in the trace logging. (Explained in Observations and Conjecture in upstream bug).
View raw text
### System details Omarchy 3, Dell XPS 9560 ### What's wrong? In the default install of Omarchy, `wl-clip-persist` is entrusted to receive (on copy) and send (on paste) clipboard data to applications. `wl-clip-persist` 0.4.3 (the latest) appears to have a condition wherein it does not complete the paste, causing the paste-receiving app to hang indefinitely. There are two workarounds: 1. Short term: From any un-hung app, copy something to the clipboard. This un-hangs the app. 2. Disable `wl-clip-persist` by commenting out the relevant line in ~/.local/share/omarchy/default/hypr/autostart.conf and logging back in (but of course you lose the benefits). Since the bug is in the upstream application, I reported it in full detail with repro steps here: https://github.com/Linus789/wl-clip-persist/issues/22 My investigation was performed using Emacs with PGTK. This is the version of Emacs that Omarchy ships under the Install->Editor->Emacs window. However, as stated in that bug, I believe the issue lies in `wl-clip-persist` because of the subtleties in the trace logging. (Explained in Observations and Conjecture in upstream bug).
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.