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.
Cursor renders as a large black square on secondary monitor
Reported by joao1barbosa · filed Mar 8, 2026Closed upstream on 2026-03-09 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 5600g, RX 6600, Omarchy 3.4.1
What's wrong?
Description
I am experiencing a persistent visual glitch where the mouse cursor appears as a large black square, specifically on my secondary monitor. This occurs across all Hyprland workspaces.
The issue first appeared after a specific interaction: I attempted to launch DBeaver on the secondary monitor while moving the mouse pointer back to the primary monitor. The application launched on the primary monitor instead, and immediately after, the cursor on the secondary monitor became corrupted.
<img src="https://github.com/user-attachments/assets/8196f4f6-fe13-4de6-ab1e-da094592e771" width="200">
Steps to Reproduce
- Connect a dual-monitor setup.
- Trigger an application launch (in this case, DBeaver) targeted at the secondary monitor.
- Quickly move the mouse cursor to the primary monitor before the window maps.
- Observe the cursor rendering on the secondary monitor.
- Expected Behavior:
The cursor should maintain its theme and scale consistently across both monitors.
- Actual Behavior:
The cursor becomes a large, solid black square on the secondary monitor. It remains functional (clicks work), but the asset is visually corrupted.
Attempted Fixes
- Restarted the Hyprland session.
- Rebooted the physical machine.
- Performed a full system update.
- The issue persists even after a clean boot.
View raw text
### System details AMD 5600g, RX 6600, Omarchy 3.4.1 ### What's wrong? ## Description I am experiencing a persistent visual glitch where the mouse cursor appears as a large black square, specifically on my secondary monitor. This occurs across all Hyprland workspaces. The issue first appeared after a specific interaction: I attempted to launch DBeaver on the secondary monitor while moving the mouse pointer back to the primary monitor. The application launched on the primary monitor instead, and immediately after, the cursor on the secondary monitor became corrupted. <img src="https://github.com/user-attachments/assets/8196f4f6-fe13-4de6-ab1e-da094592e771" width="200"> ## Steps to Reproduce 1. Connect a dual-monitor setup. 2. Trigger an application launch (in this case, DBeaver) targeted at the secondary monitor. 3. Quickly move the mouse cursor to the primary monitor before the window maps. 4. Observe the cursor rendering on the secondary monitor. - **Expected Behavior**: The cursor should maintain its theme and scale consistently across both monitors. - **Actual Behavior**: The cursor becomes a large, solid black square on the secondary monitor. It remains functional (clicks work), but the asset is visually corrupted. ## Attempted Fixes - Restarted the Hyprland session. - Rebooted the physical machine. - Performed a full system update. - The issue persists even after a clean boot.
- 8196f4f6-fe13-4de6-ab1e-da094592e771
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.