Remove NVIDIA userspace pulled onto an AMD or Intel-only machine, which hijacks OpenGL and EGL
The mechanism and fix hold on 4.0.4-1. /usr/share/omarchy/bin/omarchy-install-gaming-steam runs omarchy-pkg-add steam before omarchy-install-gaming-gpu-lib32, and omarchy-pkg-add runs pacman -S --noconfirm --needed. Arch package JSON shows nvidia-utils provides opengl-driver and vulkan-driver, and multilib lib32-nvidia-utils provides lib32-vulkan-driver and depends on nvidia-utils. nvidia-utils owns /usr/share/glvnd/egl_vendor.d/10_nvidia.json. The install.ai.ollama entry in default/omarchy/omarchy-menu.jsonc picks ollama-cuda whenever nvidia-smi exists. linux-firmware depends on linux-firmware-nvidia. ollama-vulkan, ollama-rocm, vulkan-radeon and multilib lib32-vulkan-radeon all resolve on archlinux.org. omarchy#12392 and #10380 are open and support their claims. The cause has gone stale: omarchy#8856 was closed on 2026-10-04 after PR #12569 merged into quattro, and the quattro omarchy-install-gaming-steam now runs the GPU-aware lib32 driver step before installing Steam. That is not in a release yet (latest is v4.0.4), and the bot comment on #8856 says already-installed NVIDIA packages are not removed and Lutris/Battle.net ordering is separate. The cause now says so, because a reader on a later release needs to know new installs are fixed and existing ones still need this cleanup. Not exercised: no packages were removed.
Do not run this on a machine that has an NVIDIA GPU, including a hybrid laptop whose dGPU is powered off and missing from a quick look: check lspci first. Removing the only Vulkan or OpenGL provider breaks Hyprland and Steam, so install the Mesa packages before removing anything.
Symptom
A machine with no NVIDIA GPU has nvidia-utils and lib32-nvidia-utils installed, and odd graphics failures follow: Brave or Chromium's GPU process crashes repeatedly (backtrace through libnvidia-egl-wayland2.so.1 and libEGL_nvidia.so.0) until the browser drops to software rendering, Minecraft or PrismLauncher dies with Driver does not support OpenGL 3.3, or Omarchy's Install > AI > Ollama menu installs ollama-cuda and about 3 GB of CUDA on an AMD card. nvidia-smi exists but says NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver.
Cause
nvidia-utils provides the virtual opengl-driver and vulkan-driver, and lib32-nvidia-utils provides lib32-vulkan-driver. steam depends on lib32-vulkan-driver, and under --noconfirm pacman takes the first provider, lib32-nvidia-utils, which hard-depends on nvidia-utils. On Omarchy 4.0.4, omarchy-install-gaming-steam installs steam before its GPU-aware omarchy-install-gaming-gpu-lib32 step, so AMD and Intel machines get the NVIDIA stack (omarchy#8856, #12392). The quattro branch fixed the order on 2026-10-04 (PR #12569, which closed #8856): the lib32 driver is installed first. That fix is not in v4.0.4, and it does not remove NVIDIA packages already installed. Lutris and Battle.net installs were noted as separate. Once installed, nvidia-utils ships /usr/share/glvnd/egl_vendor.d/10_nvidia.json, which libglvnd tries before Mesa's 50_mesa.json, so EGL context creation goes to the NVIDIA libraries first. The Ollama menu entry in default/omarchy/omarchy-menu.jsonc picks ollama-cuda whenever the nvidia-smi command exists, which is true here (omarchy#10380, still the case in 4.0.4).
Fix
Confirm there is no NVIDIA hardware and see what pulled the packages in:
lspci | grep -iE 'vga|3d|display'
pacman -Qi nvidia-utils lib32-nvidia-utils | grep -E '^(Name|Required By|Install Reason)'
ls /usr/share/glvnd/egl_vendor.d/
Install the Mesa providers for your GPU FIRST, so the virtual dependencies stay satisfied:
# AMD
sudo pacman -S --needed mesa lib32-mesa vulkan-radeon lib32-vulkan-radeon
# Intel
sudo pacman -S --needed mesa lib32-mesa vulkan-intel lib32-vulkan-intel
Then remove the NVIDIA userspace. Preview it first:
sudo pacman -Rsp lib32-nvidia-utils nvidia-utils
sudo pacman -Rs lib32-nvidia-utils nvidia-utils
If pacman refuses because some package still needs a provider, read which one and install its Mesa equivalent rather than forcing with -Rdd. Leave linux-firmware-nvidia alone: the linux-firmware meta package depends on it.
If the Ollama menu installed ollama-cuda on an AMD card, swap the backend:
sudo pacman -Rns ollama-cuda
sudo pacman -S --needed ollama-vulkan # or ollama-rocm
Fully quit and restart the browser. Chromium's fall-back to software rendering after repeated GPU process crashes lasts only for that run, so a normal restart clears it once the NVIDIA libraries are gone. Check chrome://gpu (or brave://gpu) afterwards.
Verify
pacman -Q nvidia-utils reports not found, ls /usr/share/glvnd/egl_vendor.d/ shows only 50_mesa.json, glxinfo -B | grep renderer (from mesa-utils) names radeonsi or Intel, and chrome://gpu in Chromium shows hardware acceleration enabled.
Sources
- https://github.com/omacom/omarchy/issues/8856
- https://github.com/omacom/omarchy/issues/12392
- https://github.com/omacom/omarchy/issues/10380
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-install-gaming-steam
- https://archlinux.org/packages/multilib/x86_64/lib32-nvidia-utils/
- https://archlinux.org/packages/extra/x86_64/nvidia-utils/