Repository navigation
Voxtype does not symlink to voxtype-vulkan on Vulkan enabled system #7099
Description
System details
AMD Radeon 780M Graphics, Omarchy Quattro
What's wrong?
When installing voxtype on a Vulkan enabled system, output shows
Error: Failed to remove existing /usr/bin/voxtype (need sudo?): Permission denied (os error 13)
Kimi K3 Root cause: voxtype setup gpu --enable rewrites the root-owned /usr/bin/voxtype symlink, but omarchy-voxtype-install ran it as your user — hence "Permission denied (os error 13)" on line 93 of the log. The trailing || true then hid the failure, so the install "succeeded" while /usr/bin/voxtype kept pointing at voxtype-avx512 instead of voxtype-vulkan. The "# omarchy:requires-sudo=true" metadata doesn't run the script as root (nor should it — the rest writes to $HOME); it's just router metadata.
Activity
omarchybot commentedon Oct 8, 2026
Thanks, @sgruendel. This is a real bug, and it is still present on
quattro(902fd8ae).bin/omarchy-voxtype-installrunsvoxtype setup gpu --enableas your user (line 19). That command has to repoint/usr/bin/voxtype, which is root-owned, so it fails with exactly the error you saw. The|| trueafter it hides the failure, and the install reports success while dictation stays on the CPU build. Theomarchy:requires-sudo=trueline in the script is only metadata for theomarchycommand menu. It does not run the script as root, and neither does the first-run invitation that launches it.The bot reproduced this on a disposable Omarchy VM with the real
voxtype-bin1.1.0 and a Vulkan driver while reviewing the fixes below. Onquattrothe switch fails withPermission denied (os error 13)and the link stays onvoxtype-avx512.Two open pull requests fix it, and both run the switch with
sudo. Both were tested the same way and moved the link tovoxtype-vulkan:voxtype-vulkanbinary, and keeps Intel Haswell GPUs on CPU because Vulkan dictation crashes there (Voxtype install enables Vulkan on Haswell (hasvk) GPUs, causing an endless SIGABRT crash loop #11370).Either one fixes this on your Radeon 780M. #11110 and #14083 report the same bug.
Reviewed by Claude Opus 5.5, with Codex Medium as a second opinion. Codex agreed with the cause and found nothing more, and it read this diagnosis before reviewing, so it was not a fully independent check.
Next step: the maintainer chooses between #12901 and #13508. Nothing is needed from you.