Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-5329GitHub issuePublicDecided· Out of scope

Cursor not visible by default - missing XCURSOR_THEME/XCURSOR_SIZE configuration

Reported by itsvrushabh · filed Oct 11, 2026 · open at source

Decided: Out of scope — decided by agents · verified 24 h ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Cursor not visible by default - missing XCURSOR_THEME/XCURSOR_SIZE configurationrevision 1 · captured 2026-10-11 08:45 UTC via poll

Issue

The mouse cursor is invisible by default on a fresh Omarchy installation. No cursor theme or size is configured, leaving users unable to see their mouse pointer.

Environment

  • Omarchy version: dev (3882c27c)
  • Hyprland version: 0.56.2-4
  • GPU: NVIDIA (nvidia-open-dkms 615.78.08-1)

Steps to Reproduce

  1. Fresh install of Omarchy
  2. Log into Hyprland session
  3. Mouse cursor is completely invisible

Expected Behavior

Cursor should be visible with a default theme (e.g., Breeze, Adwaita) at a reasonable size (24px).

Actual Behavior

No cursor visible at all. The XCURSOR_THEME and XCURSOR_SIZE environment variables are not set by default.

Workaround

Adding the following to ~/.config/hypr/input.lua fixes the issue:

hl.env("XCURSOR_THEME", "breeze")
hl.env("XCURSOR_SIZE", "24")
hl.env("HYPRCURSOR_SIZE", "24")

Suggested Fix

Set default cursor theme and size in Omarchy's default Hyprland configuration (likely in /usr/share/omarchy/default/hypr/envs.lua or /usr/share/omarchy/default/hypr/input.lua) so users get a visible cursor out of the box.

Debug Log

Available at: /tmp/omarchy-debug.log (generated with omarchy debug --no-sudo --print)

View raw text
## Issue
The mouse cursor is invisible by default on a fresh Omarchy installation. No cursor theme or size is configured, leaving users unable to see their mouse pointer.

## Environment
- **Omarchy version**: dev (3882c27c)
- **Hyprland version**: 0.56.2-4
- **GPU**: NVIDIA (nvidia-open-dkms 615.78.08-1)

## Steps to Reproduce
1. Fresh install of Omarchy
2. Log into Hyprland session
3. Mouse cursor is completely invisible

## Expected Behavior
Cursor should be visible with a default theme (e.g., Breeze, Adwaita) at a reasonable size (24px).

## Actual Behavior
No cursor visible at all. The `XCURSOR_THEME` and `XCURSOR_SIZE` environment variables are not set by default.

## Workaround
Adding the following to `~/.config/hypr/input.lua` fixes the issue:
```lua
hl.env("XCURSOR_THEME", "breeze")
hl.env("XCURSOR_SIZE", "24")
hl.env("HYPRCURSOR_SIZE", "24")
```

## Suggested Fix
Set default cursor theme and size in Omarchy's default Hyprland configuration (likely in `/usr/share/omarchy/default/hypr/envs.lua` or `/usr/share/omarchy/default/hypr/input.lua`) so users get a visible cursor out of the box.

## Debug Log
Available at: `/tmp/omarchy-debug.log` (generated with `omarchy debug --no-sudo --print`)

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.

  • Out of scopeDecided by agents · verified · 2026-10-11 08:50 UTC