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.
omarchy-install-editor-zed installs nvidia-utils on non-NVIDIA systems (no Vulkan driver for virtio-gpu)
Reported by come-maiz · filed Oct 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
What happened
On a QEMU/KVM guest with a virtio-gpu (no NVIDIA hardware), installing Zed from the
Omarchy menu (Install → Editor → Zed) pulled in nvidia-utils as a dependency:
[2026-09-24T09:55:40-0600] [PACMAN] Running 'pacman -S --noconfirm --needed zed omazed'
...
[2026-09-24T09:56:31-0600] [ALPM] installed nvidia-utils (610.57.04-1)
zed depends on vulkan-driver. No Vulkan driver was installed for this GPU, soomarchy-pkg-add (pacman -S --noconfirm) let pacman pick the first provider,nvidia-utils.
The root cause is install/hardware/vulkan.sh, which only maps Intel → vulkan-intel,
AMD → vulkan-radeon, Apple → vulkan-asahi. A virtio GPU (lspci: "Red Hat, Inc. Virtio 1.0 GPU")
gets no Vulkan driver, so any later package that needs vulkan-driver resolves to NVIDIA's.
Impact
The system ends up with NVIDIA's EGL/Vulkan vendor files
(/usr/share/glvnd/egl_vendor.d/10_nvidia.json, /usr/share/vulkan/icd.d/nvidia_icd.json)
as the only Vulkan ICD, and no nvidia kernel module. In my case the Android emulator
(-gpu host) loaded libnvidia-glcore/glsi/gpucomp and aborted ingfxstream::host::FrameBuffer::Impl::Create. I believe the NVIDIA driver caused that abort,
but I haven't confirmed it (the fatal message itself wasn't captured). The wrong-driver
install stands on its own either way.
Expected
Non-NVIDIA systems should not get nvidia-utils. Either:
- vulkan.sh installs vulkan-virtio for virtio GPUs (and possibly vulkan-swrast
as a fallback when no vendor matches), and/or
- installers that pull in vulkan-driver consumers pick a sensible provider instead of
letting --noconfirm choose the first one.
Steps to reproduce
- Install Omarchy in a QEMU/KVM VM with
-device virtio-vga-gl(virgl). - Omarchy menu → Install → Editor → Zed.
pacman -Qi nvidia-utils→ installed, "Installed as a dependency for another package",
required by zed.
System
- Omarchy 4.0.4-1
- Kernel 7.2.5-3-omarchy
- GPU: Red Hat Virtio 1.0 GPU (virtio-pci), kernel reports
+virgl - mesa 1:26.2.2-1, nvidia-utils 610.57.04-1, vulkan-icd-loader 1.4.357.0-1
Workaround
sudo pacman -S vulkan-virtio && sudo pacman -Rdd nvidia-utils
Filed by Claude Opus 5.5 via Claude Code.
View raw text
## What happened
On a QEMU/KVM guest with a virtio-gpu (no NVIDIA hardware), installing Zed from the
Omarchy menu (Install → Editor → Zed) pulled in `nvidia-utils` as a dependency:
[2026-09-24T09:55:40-0600] [PACMAN] Running 'pacman -S --noconfirm --needed zed omazed'
...
[2026-09-24T09:56:31-0600] [ALPM] installed nvidia-utils (610.57.04-1)
`zed` depends on `vulkan-driver`. No Vulkan driver was installed for this GPU, so
`omarchy-pkg-add` (`pacman -S --noconfirm`) let pacman pick the first provider,
`nvidia-utils`.
The root cause is `install/hardware/vulkan.sh`, which only maps Intel → vulkan-intel,
AMD → vulkan-radeon, Apple → vulkan-asahi. A virtio GPU (`lspci`: "Red Hat, Inc. Virtio 1.0 GPU")
gets no Vulkan driver, so any later package that needs `vulkan-driver` resolves to NVIDIA's.
## Impact
The system ends up with NVIDIA's EGL/Vulkan vendor files
(`/usr/share/glvnd/egl_vendor.d/10_nvidia.json`, `/usr/share/vulkan/icd.d/nvidia_icd.json`)
as the only Vulkan ICD, and no nvidia kernel module. In my case the Android emulator
(`-gpu host`) loaded libnvidia-glcore/glsi/gpucomp and aborted in
`gfxstream::host::FrameBuffer::Impl::Create`. I believe the NVIDIA driver caused that abort,
but I haven't confirmed it (the fatal message itself wasn't captured). The wrong-driver
install stands on its own either way.
## Expected
Non-NVIDIA systems should not get `nvidia-utils`. Either:
- `vulkan.sh` installs `vulkan-virtio` for virtio GPUs (and possibly `vulkan-swrast`
as a fallback when no vendor matches), and/or
- installers that pull in `vulkan-driver` consumers pick a sensible provider instead of
letting `--noconfirm` choose the first one.
## Steps to reproduce
1. Install Omarchy in a QEMU/KVM VM with `-device virtio-vga-gl` (virgl).
2. Omarchy menu → Install → Editor → Zed.
3. `pacman -Qi nvidia-utils` → installed, "Installed as a dependency for another package",
required by zed.
## System
- Omarchy 4.0.4-1
- Kernel 7.2.5-3-omarchy
- GPU: Red Hat Virtio 1.0 GPU (virtio-pci), kernel reports `+virgl`
- mesa 1:26.2.2-1, nvidia-utils 610.57.04-1, vulkan-icd-loader 1.4.357.0-1
## Workaround
`sudo pacman -S vulkan-virtio && sudo pacman -Rdd nvidia-utils`
---
Filed by Claude Opus 5.5 via Claude Code.
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 22:13 UTC