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.
hyprpm update stuck after upgrading to 3.1.7
Reported by opajanvv · filed Nov 10, 2025Closed upstream on 2025-11-11 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
HP Zbook Fury G8
What's wrong?
After upgrading the monitor-split-workspaces plugin doesn't load anymore.hyprpm update ends up with an error asking to run the update again. I'm stuck in a loop,
~ ❯ hyprpm update
Place your finger on the fingerprint reader
! Cloning https://github.com/hyprwm/Hyprland, this might take a moment.
✔ Hyprland cloned
✔ checked out to running ver
! configuring Hyprland
✔ configured Hyprland
✖ failed to install headers with error code 4 (Headers version mismatched)
→ if the problem persists, try running hyprpm purge-cache.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5 / 5 Failed
✖ Headers version mismatch. Please run hyprpm update to fix those.
~ ❯ hyprctl version
Hyprland 0.52.0 built from branch unknown at commit unknown unknown (unknown).
Date: unknown
Tag: unknown, commits: 0
Libraries:
Hyprgraphics: built against 0.3.0, system has 0.3.0
Hyprutils: built against 0.10.1, system has 0.10.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.3, system has 0.6.3
Aquamarine: built against 0.9.5, system has 0.9.5
no flags were setI googled a bit around, and it seems that there's a newer version 0.52.1 of hyprland that fixes this issue.
I tried to install the -git versions of the hyprland tools, but that is not successful.
View raw text
### System details HP Zbook Fury G8 ### What's wrong? After upgrading the monitor-split-workspaces plugin doesn't load anymore. `hyprpm update` ends up with an error asking to run the update again. I'm stuck in a loop, ``` ~ ❯ hyprpm update Place your finger on the fingerprint reader ! Cloning https://github.com/hyprwm/Hyprland, this might take a moment. ✔ Hyprland cloned ✔ checked out to running ver ! configuring Hyprland ✔ configured Hyprland ✖ failed to install headers with error code 4 (Headers version mismatched) → if the problem persists, try running hyprpm purge-cache. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5 / 5 Failed ✖ Headers version mismatch. Please run hyprpm update to fix those. ~ ❯ hyprctl version Hyprland 0.52.0 built from branch unknown at commit unknown unknown (unknown). Date: unknown Tag: unknown, commits: 0 Libraries: Hyprgraphics: built against 0.3.0, system has 0.3.0 Hyprutils: built against 0.10.1, system has 0.10.1 Hyprcursor: built against 0.1.13, system has 0.1.13 Hyprlang: built against 0.6.3, system has 0.6.3 Aquamarine: built against 0.9.5, system has 0.9.5 no flags were set ``` I googled a bit around, and it seems that there's a newer version 0.52.1 of hyprland that fixes this issue. I tried to install the -git versions of the hyprland tools, but that is not successful.
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.