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.
Zed fails to start on Omarchy Linux due to missing Vulkan driver (AMD Barcelo APU)
Reported by ebaerwald · filed Oct 8, 2025Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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
System details
AMD Ryzen 5 5625U, AMD Ryzen 7 Barcelo APU (integrated Radeon GPU), Omarchy v3.0.2
What's wrong?
Zed fails to start on my system (Omarchy Linux, AMD APU). The process runs indefinitely without showing a window. The Zed.log only shows repeated “starting zed” messages with no further output.
`2025-10-08T19:08:53+02:00 INFO [zed] ========== starting zed version 0.206.7, sha unknown ==========
(repeats multiple times)`
After investigation, the issue appears to be caused by missing Vulkan drivers for the integrated AMD GPU on this distribution’s default installation.
vulkaninfo | less
`ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR: vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILED
`
Workaround
Manually installing the AMD Vulkan stack fixes the issue:
`sudo pacman -S vulkan-radeon mesa mesa-vdpau lib32-vulkan-radeon lib32-mesa
`
After that, vulkaninfo detects the GPU correctly, and zeditor starts normally.
Omarchy’s installer seems to omit Vulkan driver packages (vulkan-radeon), even though the amdgpu kernel driver is present.
View raw text
### System details AMD Ryzen 5 5625U, AMD Ryzen 7 Barcelo APU (integrated Radeon GPU), Omarchy v3.0.2 ### What's wrong? Zed fails to start on my system (Omarchy Linux, AMD APU). The process runs indefinitely without showing a window. The Zed.log only shows repeated “starting zed” messages with no further output. `2025-10-08T19:08:53+02:00 INFO [zed] ========== starting zed version 0.206.7, sha unknown ========== (repeats multiple times)` After investigation, the issue appears to be caused by missing Vulkan drivers for the integrated AMD GPU on this distribution’s default installation. `vulkaninfo | less` `ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config ERROR: vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILED ` **Workaround** Manually installing the AMD Vulkan stack fixes the issue: `sudo pacman -S vulkan-radeon mesa mesa-vdpau lib32-vulkan-radeon lib32-mesa ` After that, vulkaninfo detects the GPU correctly, and zeditor starts normally. Omarchy’s installer seems to omit Vulkan driver packages (vulkan-radeon), even though the amdgpu kernel driver is present.
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.