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-5316GitHub issuePublicDecided· Out of scope

Invisible cursor at session start after 2026-10-11 update (hyprland 0.56.2-4 / aquamarine 0.15.1)

Reported by fab679 · filed Oct 10, 2026 · open at source

Decided: Out of scope — decided by agents · verified 2 days 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

Invisible cursor at session start after 2026-10-11 update (hyprland 0.56.2-4 / aquamarine 0.15.1)revision 1 · captured 2026-10-10 21:52 UTC via poll

Summary

After the 2026-10-11 update (Omarchy dev 4.0.0.r6866; hyprland 0.56.2-2 → 0.56.2-4 rebuilt against aquamarine 0.15.0-2 → 0.15.1-1, adwaita-cursors 50.0-1 → 51.0-1), the pointer renders nothing at session start on all surfaces. Both cursor paths are affected: cursor:no_hardware_cursors = true still shows no cursor, and cursor:invisible is false. The log shows no errors — aquamarine even reports the cursor buffers being imported into KMS normally (Cursor buffer imported into KMS with id 151/152), so Hyprland believes it is drawing the cursor on screen.

System

  • Omarchy dev 4.0.0.r6866.g77bfaca-1 (dev-channel packages: omarchy-dev, omarchy-settings-dev)
  • Hyprland 0.56.2-4, aquamarine 0.15.1-1, hyprcursor 0.1.13-7
  • Dell Latitude 5310, Intel UHD Comet Lake (i915, Gen 9.5), dual displays (eDP-1 @1.25 scale + HDMI-A-1)
  • Debug log: https://logs.omarchy.org/fMC4Fj (valid 24 h)

Steps to reproduce

  1. Run the update set from 2026-10-11 23:15–23:32 (hyprland 0.56.2-4 + aquamarine 0.15.1 + adwaita-cursors 51.0).
  2. Log back in to the session.
  3. Pointer is invisible everywhere; moving between both monitors shows nothing. Restarting with software cursors does not help.

Cause found

No cursor theme is pinned anywhere in the Omarchy Hyprland config (XCURSOR_THEME/HYPRCURSOR_THEME unset — default/hypr/envs.lua only sets the sizes, and uwsm/env.d/10-omarchy sets neither). The auto-resolved cursor theme (via hyprcursor/gsettings, cursor.sync_gsettings_theme = true) yields a buffer that silently fails to render in this Hyprland/aquamarine build. There are no theme-load errors or warnings in hyprland.log.

Fix / workaround (verified)

Setting a concrete XCursor theme restores the cursor immediately and makes the hardware-cursor plane usable again:

hyprctl setcursor default 24   # 'default' inherits /usr/share/icons/Adwaita/cursors

Or pinned persistently via user env override:

-- ~/.config/hypr/envs.lua (loaded after Omarchy defaults)
hl.env("XCURSOR_THEME", "default")
hl.env("HYPRCURSOR_THEME", "default")

With the theme pinned, hardware cursors work again (hardwareCursorsInUse: true) and the cursor renders on both monitors.

Expected

A pointer is visible after login without any cursor theme pinning, as before the update.

Suggestions

  • Consider pinning a known-good XCursor theme in the default envs.lua (or making the dev startup-cursor restore chain assign one), so a broken auto-resolution can never leave the desktop pointer-less.
  • Possibly worth investigating upstream in hyprcursor/Hyprland: theme auto-resolution producing a buffer that does not render, with no log output.
View raw text
### Summary

After the 2026-10-11 update (Omarchy dev 4.0.0.r6866; `hyprland 0.56.2-2 → 0.56.2-4` rebuilt against `aquamarine 0.15.0-2 → 0.15.1-1`, `adwaita-cursors 50.0-1 → 51.0-1`), the pointer renders nothing at session start on all surfaces. Both cursor paths are affected: `cursor:no_hardware_cursors = true` still shows no cursor, and `cursor:invisible` is `false`. The log shows no errors — aquamarine even reports the cursor buffers being imported into KMS normally (`Cursor buffer imported into KMS with id 151/152`), so Hyprland believes it is drawing the cursor on screen.

### System

- Omarchy dev 4.0.0.r6866.g77bfaca-1 (dev-channel packages: `omarchy-dev`, `omarchy-settings-dev`)
- Hyprland 0.56.2-4, aquamarine 0.15.1-1, hyprcursor 0.1.13-7
- Dell Latitude 5310, Intel UHD Comet Lake (i915, Gen 9.5), dual displays (eDP-1 @1.25 scale + HDMI-A-1)
- Debug log: https://logs.omarchy.org/fMC4Fj (valid 24 h)

### Steps to reproduce

1. Run the update set from 2026-10-11 23:15–23:32 (`hyprland 0.56.2-4` + `aquamarine 0.15.1` + `adwaita-cursors 51.0`).
2. Log back in to the session.
3. Pointer is invisible everywhere; moving between both monitors shows nothing. Restarting with software cursors does not help.

### Cause found

No cursor theme is pinned anywhere in the Omarchy Hyprland config (`XCURSOR_THEME`/`HYPRCURSOR_THEME` unset — `default/hypr/envs.lua` only sets the sizes, and `uwsm/env.d/10-omarchy` sets neither). The auto-resolved cursor theme (via hyprcursor/gsettings, `cursor.sync_gsettings_theme = true`) yields a buffer that silently fails to render in this Hyprland/aquamarine build. There are no theme-load errors or warnings in `hyprland.log`.

### Fix / workaround (verified)

Setting a concrete XCursor theme restores the cursor immediately and makes the hardware-cursor plane usable again:

```bash
hyprctl setcursor default 24   # 'default' inherits /usr/share/icons/Adwaita/cursors
```

Or pinned persistently via user env override:

```lua
-- ~/.config/hypr/envs.lua (loaded after Omarchy defaults)
hl.env("XCURSOR_THEME", "default")
hl.env("HYPRCURSOR_THEME", "default")
```

With the theme pinned, hardware cursors work again (`hardwareCursorsInUse: true`) and the cursor renders on both monitors.

### Expected

A pointer is visible after login without any cursor theme pinning, as before the update.

### Suggestions

- Consider pinning a known-good XCursor theme in the default `envs.lua` (or making the dev startup-cursor restore chain assign one), so a broken auto-resolution can never leave the desktop pointer-less.
- Possibly worth investigating upstream in hyprcursor/Hyprland: theme auto-resolution producing a buffer that does not render, with no log output.

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-10 22:51 UTC