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.
Ollama install menu picks CUDA/CPU on AMD systems: `nvidia-smi` presence ≠ NVIDIA GPU, and the `rocminfo` branch never fires
Reported by bel-maty · filed Sep 5, 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?
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
System details
omarchy 4.0.2-1, Hyprland 0.56.2-1 - GPU: AMD Radeon RX 7900 XT — Navi 31 [1002:744c], amdgpu, gfx1100 - mesa 1:26.2.1-1, vulkan-radeon 1:26.2.1-1 - nvidia-utils 610.57.04-1 present (pulled in as a dependency of hyprland / aquamarine / steam / lib32-nvidia-utils / umu-launcher); no NVIDIA hardware; no ROCm packages installed
What's wrong?
What happened
On an AMD-only machine (Radeon RX 7900 XT, amdgpu), Menu → Install → AI → Ollama
installed ollama-cuda plus the full cuda dependency tree (~3 GB installed)
instead of ollama-rocm.
Root cause
default/omarchy/omarchy-menu.jsonc, entry install.ai.ollama:
if omarchy-cmd-present nvidia-smi; then ollama_pkg=ollama-cuda;
elif omarchy-cmd-present rocminfo; then ollama_pkg=ollama-rocm;
else ollama_pkg=ollama; fiTwo problems:
- `nvidia-smi` present ≠ NVIDIA GPU.
nvidia-utilsships/usr/bin/nvidia-smi
and is routinely pulled onto AMD/Intel machines as an opengl-driver /
vulkan-driver provider. On this box it is a dependency of hyprland,
aquamarine, steam, lib32-nvidia-utils, and umu-launcher.
omarchy-cmd-present nvidia-smi (i.e. command -v nvidia-smi) therefore
succeeds on hardware with no NVIDIA GPU, and the menu installs ollama-cuda.
Note nvidia-smi -L itself fails here with *"NVIDIA-SMI has failed because it
couldn't communicate with the NVIDIA driver"* — so even checking the command's
exit status, not just its presence, would avoid this.
- The `rocminfo` branch is effectively dead.
rocminfocomes from the
rocminfo / rocm-core package, which a stock Omarchy install never places on
disk — AMD systems get mesa + vulkan-radeon (see
install/hardware/vulkan.sh), not ROCm. ollama-rocm does not depend on
rocminfo either. So via this menu an AMD GPU owner gets ollama-cuda (if any
nvidia-utils is present) or the CPU-only ollama — but never ollama-rocm.
Expected
AMD GPU → ollama-rocm; NVIDIA GPU → ollama-cuda; otherwise → ollama.
Suggested fix
Detect by hardware vendor, the way install/hardware/nvidia.sh andinstall/hardware/vulkan.sh already do, instead of probing for userspace
binaries:
if lspci | grep -qiE '(VGA|3D|Display).*NVIDIA'; then
ollama_pkg=ollama-cuda
elif lspci | grep -qiE '(VGA|3D|Display).*(AMD|ATI)'; then
ollama_pkg=ollama-rocm
else
ollama_pkg=ollama
fiGating on the loaded kernel module (nvidia vs amdgpu) would work equally well.
A machine with both GPUs should probably prefer whichever the compositor is
actually running on.
Repro
- Any AMD-GPU machine that also has
nvidia-utilsinstalled — common, since
Steam or anything that resolved the virtual opengl-driver / vulkan-driver
to nvidia-utils drags it in.
2. Menu → Install → AI → Ollama.
3. ollama-cuda + cuda are installed instead of ollama-rocm.
View raw text
### System details omarchy 4.0.2-1, Hyprland 0.56.2-1 - GPU: AMD Radeon RX 7900 XT — Navi 31 `[1002:744c]`, `amdgpu`, gfx1100 - mesa 1:26.2.1-1, vulkan-radeon 1:26.2.1-1 - nvidia-utils 610.57.04-1 present (pulled in as a dependency of hyprland / aquamarine / steam / lib32-nvidia-utils / umu-launcher); no NVIDIA hardware; no ROCm packages installed ### What's wrong? ## What happened On an AMD-only machine (Radeon RX 7900 XT, `amdgpu`), **Menu → Install → AI → Ollama** installed `ollama-cuda` plus the full `cuda` dependency tree (~3 GB installed) instead of `ollama-rocm`. ## Root cause `default/omarchy/omarchy-menu.jsonc`, entry `install.ai.ollama`: ```sh if omarchy-cmd-present nvidia-smi; then ollama_pkg=ollama-cuda; elif omarchy-cmd-present rocminfo; then ollama_pkg=ollama-rocm; else ollama_pkg=ollama; fi ``` Two problems: 1. **`nvidia-smi` present ≠ NVIDIA GPU.** `nvidia-utils` ships `/usr/bin/nvidia-smi` and is routinely pulled onto AMD/Intel machines as an `opengl-driver` / `vulkan-driver` provider. On this box it is a dependency of `hyprland`, `aquamarine`, `steam`, `lib32-nvidia-utils`, and `umu-launcher`. `omarchy-cmd-present nvidia-smi` (i.e. `command -v nvidia-smi`) therefore succeeds on hardware with no NVIDIA GPU, and the menu installs `ollama-cuda`. Note `nvidia-smi -L` itself fails here with *"NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver"* — so even checking the command's exit status, not just its presence, would avoid this. 2. **The `rocminfo` branch is effectively dead.** `rocminfo` comes from the `rocminfo` / `rocm-core` package, which a stock Omarchy install never places on disk — AMD systems get `mesa` + `vulkan-radeon` (see `install/hardware/vulkan.sh`), not ROCm. `ollama-rocm` does not depend on `rocminfo` either. So via this menu an AMD GPU owner gets `ollama-cuda` (if any `nvidia-utils` is present) or the CPU-only `ollama` — but never `ollama-rocm`. ## Expected AMD GPU → `ollama-rocm`; NVIDIA GPU → `ollama-cuda`; otherwise → `ollama`. ## Suggested fix Detect by hardware vendor, the way `install/hardware/nvidia.sh` and `install/hardware/vulkan.sh` already do, instead of probing for userspace binaries: ```sh if lspci | grep -qiE '(VGA|3D|Display).*NVIDIA'; then ollama_pkg=ollama-cuda elif lspci | grep -qiE '(VGA|3D|Display).*(AMD|ATI)'; then ollama_pkg=ollama-rocm else ollama_pkg=ollama fi ``` Gating on the loaded kernel module (`nvidia` vs `amdgpu`) would work equally well. A machine with both GPUs should probably prefer whichever the compositor is actually running on. ## Repro 1. Any AMD-GPU machine that also has `nvidia-utils` installed — common, since Steam or anything that resolved the virtual `opengl-driver` / `vulkan-driver` to `nvidia-utils` drags it in. 2. Menu → Install → AI → Ollama. 3. `ollama-cuda` + `cuda` are installed instead of `ollama-rocm`.
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
- Related PRpr/11691· confirmed
- Fixed bypr/10472· confirmed
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.
- Decided by agents · verified: in the audited area (menu)
- Decided by agents · verified: matches no known issue
The outcome (valid, duplicate, not a bug, …) is not decided yet.