## Summary

Omarchy currently appears to be unusable when installed as a guest in VMware Workstation with VMware 3D acceleration enabled.

The system boots and Hyprland starts, but the graphical desktop renders as a black screen with only the mouse cursor visible.

This appears to be related to the Hyprland/Aquamarine interaction with VMware's `vmwgfx` graphics stack rather than a general failure of VMware 3D acceleration.

## Environment

- Omarchy
- Hyprland
- VMware Workstation
- VMware SVGA II virtual GPU
- Linux `vmwgfx` kernel driver
- Mesa 26.1.7
- Wayland
- Quickshell (Omarchy desktop shell)

GPU:

    VMware SVGA II Adapter [15ad:0405]
    Kernel driver: vmwgfx

## Primary failure

With VMware 3D acceleration enabled, the Omarchy graphical session starts but the desktop is not usable.

The visible result is:

- black screen
- mouse cursor visible
- no functional Omarchy desktop

This occurs even though the VMware GPU and 3D acceleration are detected correctly.

Mesa reports:

    OpenGL core profile vendor: VMware, Inc.
    OpenGL core profile renderer: SVGA3D; build: RELEASE; LLVM;
    OpenGL core profile version: 4.3 (Core Profile) Mesa 26.1.7

The VMware DRM driver also reports 3D capability.

## Quickshell / Omarchy shell

Quickshell is running:

    quickshell -n -p /usr/share/omarchy/shell

and the Wayland socket exists:

    /run/user/1000/wayland-1

However, the Omarchy shell does not render correctly in the accelerated configuration.

A partial workaround is possible by forcing software rendering for Quickshell:

    WAYLAND_DISPLAY=wayland-1 \
    XDG_RUNTIME_DIR=/run/user/1000 \
    QT_QPA_PLATFORM=wayland \
    QSG_RHI_BACKEND=software \
    quickshell -n -p /usr/share/omarchy/shell

This demonstrates that the accelerated rendering path is implicated, but this is not a practical general solution.

## Wayland client failures

Native Wayland applications can also lose their connection to Hyprland.

For example, Ghostty starts with its OpenGL renderer:

    info: renderer=renderer.generic.Renderer(renderer.OpenGL)

but subsequently reports:

    Gdk: Lost connection to Wayland compositor.

Hyprland reports:

    unknown object (61), message attach(?oii)
    error in client communication

This does not appear to be Ghostty-specific.

## Related issues

There are already VMware-related Omarchy reports:

- Omarchy #1176 — BUG: Wayland Drivers - Omarchy 2.0 in VMs
  https://github.com/basecamp/omarchy/issues/1176

- Omarchy Discussion #572 — Omarchy on VMware Workstation
  https://github.com/basecamp/omarchy/discussions/572

The underlying issue appears particularly closely related to this Hyprland discussion:

- Hyprland Discussion #12966
  https://github.com/hyprwm/Hyprland/discussions/12966

That discussion specifically concerns Hyprland running under VMware with `vmwgfx` and Wayland clients failing, and references a patch that reportedly addresses the VMware/vmwgfx compatibility problem.

## Why this matters

A user attempting to evaluate or use Omarchy inside VMware Workstation is likely to encounter this problem if VMware 3D acceleration is enabled.

The expected sequence is:

1. Install Omarchy in VMware Workstation.
2. Enable VMware 3D acceleration.
3. Boot successfully into the graphical session.
4. Hyprland starts.
5. Screen remains black except for the mouse cursor.
6. Omarchy's Quickshell UI does not render.
7. Native Wayland applications may subsequently fail with compositor/client communication errors.

Software rendering can make portions of the environment usable, but this defeats the purpose of VMware 3D acceleration and is not an acceptable general solution.

## Requested action

Please investigate whether the Hyprland/Aquamarine fix discussed in Hyprland #12966 has been incorporated into the versions currently shipped by Omarchy.

If it has not yet landed upstream, it would be useful to:

- track this compatibility issue from the Omarchy side;
- determine whether the referenced patch is applicable to the current Hyprland/Aquamarine versions;
- consider incorporating the fix when appropriate; and
- document VMware Workstation compatibility if the issue cannot currently be resolved.

VMware Workstation should otherwise be considered a significant deployment/testing environment for Omarchy, and currently the accelerated configuration does not provide a functional desktop.