OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors low common DISPUTE

Fix a cursor that changes size between mixed-DPI monitors

omarchyarchendeavouroscachyoshyprlandwaylandnvidialaptopdesktop
AUDITED Audited against its sources and confirmed accurate.

Symptom

The mouse cursor is a tiny speck on the 4K screen and a giant arrow on the 1080p one, or it changes size the moment it crosses between monitors. Sometimes the cursor is completely invisible over XWayland windows or in a VM.

Cause

XCursor themes are bitmaps at fixed sizes, so a single XCURSOR_SIZE cannot be right on two displays with different scales. Omarchy ships XCURSOR_SIZE=24 and HYPRCURSOR_SIZE=24 in /usr/share/omarchy/default/hypr/envs.lua. Invisible cursors are usually a hardware-cursor plane the driver cannot commit (vmwgfx, some virtual GPUs).

Fix

Set both sizes together. They must agree, or the cursor changes size between Wayland-native and XWayland surfaces. In ~/.config/hypr/looknfeel.lua (or your own Hyprland config):


hl.env("XCURSOR_SIZE", "32")
hl.env("HYPRCURSOR_SIZE", "32")

On Hyprland <= 0.54: env = XCURSOR_SIZE,32 and env = HYPRCURSOR_SIZE,32.

Keep GTK's own setting in sync so CSD apps agree:


gsettings set org.gnome.desktop.interface cursor-size 32

For an invisible cursor (VMs, vmwgfx, some NVIDIA setups), fall back to a software cursor:


hl.config({ cursor = { no_hardware_cursors = 1 } })

On NVIDIA, hardware cursors need cursor.use_cpu_buffer (default 2 = auto-on for NVIDIA). Set it to 1 if the cursor is corrupt.

Log out and back in for the env change to reach already-running apps.

Verify

The cursor is the same apparent physical size on both monitors and stays visible over XWayland windows.

Sources

cursor-wrong-size-on-scaled-or-mixed-monitors