Nautilus starts and exits without a window on a VMware SVGA display. The keybindings menu entry for File Manager and Super+Shift+F both call omarchy-launch-nautilus, so both look dead.
Two things combine. The session sets GDK_BACKEND=wayland,x11,*, and this Nautilus build then aborts its Wayland connection (Unsupported or missing session type 'wayland'). The SVGA adapter also has no usable Vulkan renderer, which is what GTK tries first. Unsetting GDK_BACKEND and launching with GSK_RENDERER=cairo maps a window. Either change alone does not.
This is limited to that display. omarchy-hw-vmware-svga matches a VMware PCI display (0x15ad, class 0x03*), the same sysfs read omarchy-hw-nvidia uses. Other machines, including other virtual machines, keep the normal launch. GDK_BACKEND stays set for the rest of the session.
Checked on a VMware Fusion guest with SVGA II 15ad:0405: after the change, Files opens a mapped Home window. test/shell.d/hw-vmware-svga-test.sh covers the detector and both launchers.
[Medium impact] The change affects Files launches on VMware SVGA displays.
The launch changes appear sound, but the explicit comparison style requirement must be satisfied before merging.
Findings
Summary
Adds a VMware SVGA detector and uses it in both Files launch commands.
Review checks were limited to reading code; no tests were run.
Reviews (1) · Last reviewed commit: "Open Files on a VMware SVGA display" · Reviewed by Greptile