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-hw-nvidia-without-gsp misclassifies Turing-based MX cards (e.g. MX550) as no-GSP, causing driver conflict with Steam install
Reported by AndresSM415 · filed Jul 14, 2026Closed upstream on 2026-10-08 by its own reporter AndresSM415. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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. No decision has been recorded yet.
Original report
\omarchy-hw-nvidia-without-gsp\ matches GPU names against \MX *[0-9]+\ unconditionally, assuming all "MX" branded cards are pre-Turing (Maxwell/Pascal/Volta, no GSP firmware):
\\\`bash
bin/omarchy-hw-nvidia-without-gsp
lspci | grep -i 'nvidia' | grep -qE "GTX (9[0-9]{2}|10[0-9]{2})|GT 10[0-9]{2}|Quadro [PM][0-9]{3,4}|Quadro GV100|MX *[0-9]+|Titan (X|Xp|V)|Tesla V100"
\\\`
But NVIDIA continued the "MX" naming into the Turing generation (e.g. MX450, MX550, MX570 are \TU117\/\TU117M\ chips — same generation as GTX 16xx, which \omarchy-hw-nvidia-gsp\ does match). On a laptop with an MX550, this causes:
- \
omarchy-hw-nvidia-without-gsp\to incorrectly return true - \
omarchy-install-gaming-gpu-lib32\(invoked during Steam install) to try installing \lib32-nvidia-580xx-utils\ - A pacman conflict, since the correct mainline \
lib32-nvidia-utils\was already installed (matching the correctly-detected mainline \nvidia-utils\driver from initial GPU setup)
Repro:
\\\`
$ lspci | grep -i vga
02:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)
$ omarchy-hw-nvidia-gsp; echo $?
1
$ omarchy-hw-nvidia-without-gsp; echo $?
0
\\\`
Suggested fix: exclude Turing-generation MX cards from the no-GSP pattern, e.g. change \MX *[0-9]+\ to only match pre-Turing models (\MX1[0-9]{2}\b|MX2[0-9]{2}\b|MX3[0-9]{2}\b\, i.e. MX110–MX350), and/or add \MX[4-9][0-9]{2}\ to the GSP-detector pattern in \omarchy-hw-nvidia-gsp\.
View raw text
\`omarchy-hw-nvidia-without-gsp\` matches GPU names against \`MX *[0-9]+\` unconditionally, assuming all "MX" branded cards are pre-Turing (Maxwell/Pascal/Volta, no GSP firmware):
\`\`\`bash
# bin/omarchy-hw-nvidia-without-gsp
lspci | grep -i 'nvidia' | grep -qE "GTX (9[0-9]{2}|10[0-9]{2})|GT 10[0-9]{2}|Quadro [PM][0-9]{3,4}|Quadro GV100|MX *[0-9]+|Titan (X|Xp|V)|Tesla V100"
\`\`\`
But NVIDIA continued the "MX" naming into the Turing generation (e.g. **MX450, MX550, MX570** are \`TU117\`/\`TU117M\` chips — same generation as GTX 16xx, which \`omarchy-hw-nvidia-gsp\` *does* match). On a laptop with an MX550, this causes:
1. \`omarchy-hw-nvidia-without-gsp\` to incorrectly return true
2. \`omarchy-install-gaming-gpu-lib32\` (invoked during Steam install) to try installing \`lib32-nvidia-580xx-utils\`
3. A pacman conflict, since the correct mainline \`lib32-nvidia-utils\` was already installed (matching the correctly-detected mainline \`nvidia-utils\` driver from initial GPU setup)
**Repro:**
\`\`\`
$ lspci | grep -i vga
02:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)
$ omarchy-hw-nvidia-gsp; echo $?
1
$ omarchy-hw-nvidia-without-gsp; echo $?
0
\`\`\`
**Suggested fix:** exclude Turing-generation MX cards from the no-GSP pattern, e.g. change \`MX *[0-9]+\` to only match pre-Turing models (\`MX1[0-9]{2}\b|MX2[0-9]{2}\b|MX3[0-9]{2}\b\`, i.e. MX110–MX350), and/or add \`MX[4-9][0-9]{2}\` to the GSP-detector pattern in \`omarchy-hw-nvidia-gsp\`.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.
No decision has been recorded yet.