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.
VMware guest: installer leaves the system without open-vm-tools (live ISO has them); plus working fix for the 3D-acceleration grey screen (#8113)
Reported by kevincasier · filed Sep 7, 2026 · open at source
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
Environment
Omarchy 4.0.2 ISO, VMware Workstation Pro 26H1u1 on Windows 11, guest with "Accelerate 3D graphics" enabled, vmwgfx 2.21.0, Hyprland 0.56.2.
1. open-vm-tools missing after install
The live ISO runs the VMware guest tools (host log shows Guest: toolbox: Version: 13.1.0.0.25218885 during the installer), but the installed system has no open-vm-tools at all: no vmtoolsd, no shared folders, no clipboard, no display integration, and the guest does not follow the VMware window size. pacman -S open-vm-tools + systemctl enable --now vmtoolsd vmware-vmblock-fuse fixes it.
Suggestion: when the installer detects a VMware guest (systemd-detect-virt = vmware), install open-vm-tools and enable vmtoolsd and vmware-vmblock-fuse, mirroring what the live ISO already does. (Same idea would apply to qemu-guest-agent/spice-vdagent for QEMU and virtualbox-guest-utils for VirtualBox if not already handled.)
2. Grey/black screen with 3D acceleration (#8113, #7835, #8604) — root cause and tested fix
This is a Hyprland bug on vmwgfx, not an Omarchy one: vmwgfx prime-imports dmabufs as TTM surface handles, drmCloseBufferHandle() (GEM_CLOSE) fails with EINVAL, Hyprland rejects every GPU client's buffer and logs Failed to close dmabuf handle ~30k times/min. Filed upstream with a patch: hyprwm/Hyprland (issue linked below). With the patched hyprland (fallback to DRM_VMW_UNREF_SURFACE), Omarchy runs fully GPU-accelerated in VMware, including multi-monitor.
Until it lands upstream, the workaround that works on Omarchy 4 is a system-wide LIBGL_ALWAYS_SOFTWARE=1 (e.g. in /etc/environment, applied by PAM to the SDDM session) or hl.env("LIBGL_ALWAYS_SOFTWARE", "1") in ~/.config/hypr/hyprland.lua. Note for the docs: the old ~/.config/hypr/envs.conf advice found in most guides does nothing on Omarchy 4 (Lua config).
3. Small things noticed on VMware, for the VM guide
- Default
omarchy_gdk_scale = 2on a 1280x800 VMware virtual display gives an effectively 640x400 desktop; a VM detection could default to 1x. - For multi-monitor under Wayland, vmusr's X11
resolutionSetplugin must not run (it steals the resolution-server role fromresolutionKMS); reported at vmware/open-vm-tools (link below).
Upstream links: Hyprland https://github.com/hyprwm/Hyprland/issues/16175 ; open-vm-tools https://github.com/vmware/open-vm-tools/issues/805
View raw text
### Environment
Omarchy 4.0.2 ISO, VMware Workstation Pro 26H1u1 on Windows 11, guest with "Accelerate 3D graphics" enabled, `vmwgfx 2.21.0`, Hyprland 0.56.2.
### 1. open-vm-tools missing after install
The live ISO runs the VMware guest tools (host log shows `Guest: toolbox: Version: 13.1.0.0.25218885` during the installer), but the installed system has no `open-vm-tools` at all: no `vmtoolsd`, no shared folders, no clipboard, no display integration, and the guest does not follow the VMware window size. `pacman -S open-vm-tools` + `systemctl enable --now vmtoolsd vmware-vmblock-fuse` fixes it.
Suggestion: when the installer detects a VMware guest (`systemd-detect-virt` = `vmware`), install `open-vm-tools` and enable `vmtoolsd` and `vmware-vmblock-fuse`, mirroring what the live ISO already does. (Same idea would apply to `qemu-guest-agent`/`spice-vdagent` for QEMU and `virtualbox-guest-utils` for VirtualBox if not already handled.)
### 2. Grey/black screen with 3D acceleration (#8113, #7835, #8604) — root cause and tested fix
This is a Hyprland bug on `vmwgfx`, not an Omarchy one: vmwgfx prime-imports dmabufs as TTM surface handles, `drmCloseBufferHandle()` (GEM_CLOSE) fails with EINVAL, Hyprland rejects every GPU client's buffer and logs `Failed to close dmabuf handle` ~30k times/min. Filed upstream with a patch: hyprwm/Hyprland (issue linked below). With the patched `hyprland` (fallback to `DRM_VMW_UNREF_SURFACE`), Omarchy runs fully GPU-accelerated in VMware, including multi-monitor.
Until it lands upstream, the workaround that works on Omarchy 4 is a **system-wide** `LIBGL_ALWAYS_SOFTWARE=1` (e.g. in `/etc/environment`, applied by PAM to the SDDM session) or `hl.env("LIBGL_ALWAYS_SOFTWARE", "1")` in `~/.config/hypr/hyprland.lua`. Note for the docs: the old `~/.config/hypr/envs.conf` advice found in most guides does nothing on Omarchy 4 (Lua config).
### 3. Small things noticed on VMware, for the VM guide
- Default `omarchy_gdk_scale = 2` on a 1280x800 VMware virtual display gives an effectively 640x400 desktop; a VM detection could default to 1x.
- For multi-monitor under Wayland, vmusr's X11 `resolutionSet` plugin must not run (it steals the resolution-server role from `resolutionKMS`); reported at vmware/open-vm-tools (link below).
Upstream links: Hyprland https://github.com/hyprwm/Hyprland/issues/16175 ; open-vm-tools https://github.com/vmware/open-vm-tools/issues/805
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-09 11:03 UTC