Zed failed to open a window: NoSupportedDeviceFound #28265
Replies: 47 comments 1 reply
-
|
Hi @lasypig:
For reference, here are the current docs for Building Zed for Linux. |
Beta Was this translation helpful? Give feedback.
-
I will try to build zed on my ubuntu. I built zed myself, but problem still exists: cargo run
warning: `/home/wangxb/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
warning: `/home/wangxb/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.58s
Running `target/debug/zed`
Zed failed to open a window: NoSupportedDeviceFoundAfter searching error string, |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue System Info $ uname -a
Linux lerssett 6.9.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 19:49:19 +0000 x86_64 GNU/Linux
$ sb_release -a
LSB Version: 2.0
Distributor ID: EndeavourOS
Description: EndeavourOS Linux
Release: rolling
Codename: rolling
$ lspci -k | grep -A 2 -E "(VGA|3D)"
01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3283
Kernel driver in use: nouveauSoftware $ pacman -Q | rg mesa
lib32-mesa 1:24.1.2-1
mesa 1:24.1.2-1
mesa-utils 9.0.0-4
vulkan-mesa-layers 1:24.1.2-1
$ pacman -Q | rg nouveau
lib32-vulkan-nouveau 1:24.1.2-1
vulkan-nouveau 1:24.1.2-1
xf86-video-nouveau 1.0.17-3
$ pacman -Q | rg zed
zed 0.140.5-1When I run command vkEnumeratePhysicalDevices reported zero accessible devices.
Do you have a compatible Vulkan installable client driver (ICD) installed?
Please look at the Getting Started guide for additional information.but it works fine with env var Zed output without that env var is $ /usr/lib/zed/zed-editor
[2024-06-26T16:47:25+02:00 ERROR zed::reliability] {
"thread": "main",
"payload": "called `Result::unwrap()` on an `Err` value: ERROR_INITIALIZATION_FAILED",
"location_data": {
"file": "/build/.cargo/git/checkouts/blade-ea462a0faa3f9995/33fd513/blade-graphics/src/vulkan/init.rs",
"line": 379
},
"backtrace": [
"__libc_start_main"
],
"app_version": "0.140.5",
"release_channel": "Zed",
"os_name": "Linux Wayland",
"os_version": "endeavouros unknown",
"architecture": "x86_64",
"panicked_on": 1719413245132,
"installation_id": "fc128855-9a2d-43c3-835e-1eb6a4361b5e",
"session_id": "2c47a610-15e2-42b6-9cba-49301796ad93"
}
fish: Job 1, '/usr/lib/zed/zed-editor' terminated by signal SIGABRT (Abort)with env var $ NVK_I_WANT_A_BROKEN_VULKAN_DRIVER=1 /usr/lib/zed/zed-editor
WARNING: NVK is not a conformant Vulkan implementation, testing use only.
Zed failed to open a window: NoSupportedDeviceFound
fish: Job 1, 'NVK_I_WANT_A_BROKEN_VULKAN_DRIV…' terminated by signal SIGSEGV (Address boundary error)vulkaninfo $ vulkaninfo
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs: Failed to detect any valid GPUs in the current config
ERROR at /usr/src/debug/vulkan-tools/Vulkan-Tools-1.3.269/vulkaninfo/./vulkaninfo.h:237:vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILEDNVK_I_WANT_A_BROKEN_VULKAN_DRIVER=1 vulkaninfohttps://gist.github.com/Stanislav-Lapata/0d188cc028d123640a7ae92d3e90d601 |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue.
|
Beta Was this translation helpful? Give feedback.
-
|
On OpenSUSE after running When I run I needed to install Then zed runs, can be used, but then crashes randomly, and I dont see where the log is. |
Beta Was this translation helpful? Give feedback.
-
|
To anyone experiencing this issue, please add the following information:
For our part we've had a couple of reports of this with the Solus package, both users affected are using hybrid Intel/Nvidia GPUs and it appears that Vulkan initialization is failing with the Intel GPU but succeeding with the Nvidia one. If anyone is having this issue with a similar configuration please try the following to isolate the issue: To force it to use the Intel GPU: For Nvidia These paths may be different depending on your distribution. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue and was able to fix by installing https://archlinux.org/packages/?name=vulkan-nouveau Linux lyminox-83ef 6.9.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 28 Jun 2024 04:32:50 +0000 x86_64 GNU/Linux
01:00.0 VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile] (rev a1)
Subsystem: Lenovo Device 3d0a
Kernel driver in use: nouveau
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 0a)
Subsystem: Lenovo Device 3d0a
Kernel driver in use: amdgpu |
Beta Was this translation helpful? Give feedback.
-
|
If anyone with an AMD GPU and Arch stumbles upon this, I had the same issue and fixed it by installing |
Beta Was this translation helpful? Give feedback.
-
|
I come from the Linux announcement in HN, and got same issue. Info:
(Here the commands I used, if others want to use them too for their reports)$ zed --version
Zed 0.143.6 – /home/work/.local/zed.app/libexec/zed-editor
$ echo "$XDG_SESSION_TYPE"
x11
$ lsb_release -d
Description: Linux Mint 20.3
$ cinnamon --version
Cinnamon 5.2.7
$ lspci -v -mm -k | sed -r -n '/Class:.*(VGA|3D)/,/^$/p'
Class: VGA compatible controller
Vendor: Intel Corporation
Device: Iris Pro Graphics 6200
SVendor: ASRock Incorporation
SDevice: Iris Pro Graphics 6200
Rev: 0a
Driver: i915
Module: i915
$ uname -r
5.15.0-107-generic
$ apt-cache policy mesa-vulkan-drivers | grep 'Installed:'
Installed: 21.2.6-0ubuntu0.1~20.04.2mesa-vulkan-drivers provides $ VK_ICD_FILENAMES='/usr/share/vulkan/icd.d/intel_icd.x86_64.json' zed .
error opening [PathLikeWithPosition { path_like: "/home/work/tmp", row: None, column: None }]: NoSupportedDeviceFound |
Beta Was this translation helpful? Give feedback.
-
|
@kvark , perhaps you might know what's going on here? Or what diagnostic information might be helpful for debugging this? |
Beta Was this translation helpful? Give feedback.
-
|
+1 on Ubuntu 20.04, |
Beta Was this translation helpful? Give feedback.
-
|
same issue here |
Beta Was this translation helpful? Give feedback.
-
|
Running Zed inside a VM failed: As workaround, |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @geraldhobbes for the advice! Then afterwards I ran it as normal and it worked, but it useed the integrated graphics and I see very high cpu usage and sluggishness. Following https://wiki.archlinux.org/title/Vulkan#Troubleshooting, as I have a dedicated nvidia gpu, I tried to to open zed as |
Beta Was this translation helpful? Give feedback.
-
|
Me too rpm -qa | grep mesa rpm -qa | grep vulkan |
Beta Was this translation helpful? Give feedback.
-
|
@sillybreakfast it would help to provide the following:
|
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue, I've installed with the recommended command |
Beta Was this translation helpful? Give feedback.
-
|
The same problem. Version of the vulkan drivers: vkcube output of zed with debug |
Beta Was this translation helpful? Give feedback.
-
|
@juanma1331 based on your vulkaninfo, this system should run just fine. I see that running Zed executable under the Rust log environment isn't working trivially - Zed forks itself immediately. cd blade
RUST_LOG=blade_graphics=info cargo run --example bunnymark |
Beta Was this translation helpful? Give feedback.
-
|
I started the installation using the command For some reason, Zed detected the emulated GPU instead of the actual one. Next, I tried to force the use of the NVIDIA GPU with the command I got the same error trying to force it using other methods. The content of {
"file_format_version" : "1.0.0",
"ICD": {
"library_path": "libGLX_nvidia.so.0",
"api_version" : "1.2.175"
}
}Zed log content: Blade example log: |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you @juanma1331, I see now that the vulkaninfo only lists support for "dynamic rendering" on the software implementation. Looks like NVidia isn't releasing a driver update for this GPU with newer Vulkan features. |
Beta Was this translation helpful? Give feedback.
-
|
the issue appeared after a kernel upgrade on fedora 40 KDE with vulkan. It resolved for me after debuggin vulkan configuration, rebuilding NVIDIA kernel modules.
sudo akmods --force
sudo dracut --force
vulkaninfo
echo $VK_ICD_FILENAMES
|
Beta Was this translation helpful? Give feedback.
-
This almost worked for me
Both A Zed window pops up but then stucks, before going all black |
Beta Was this translation helpful? Give feedback.
-
Now it works without any additional actions!
|
Beta Was this translation helpful? Give feedback.
-
did you solve this? I'm getting a similar error: On debian with x11 |
Beta Was this translation helpful? Give feedback.
-
You need to update to a newer distribution if you want Zed to work. Edit: I notice you did say Debian, so my guess about Bullseye is probably correct. You could try Bookworm, that has Mesa 22.3.6 which might work otherwise there's 24.2.4 in backports. |
Beta Was this translation helpful? Give feedback.
-
|
I have experienced the same issue today
What solve this problem for me is to set the variable below inside my export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.jsonEDIT : The root cause was an incorrectly configured XDG_DATA_DIRS. After noticing multiple apps were affected, I fixed it by adding |
Beta Was this translation helpful? Give feedback.
-
|
@ReillyBrogan you where right, i switched from debian bullseye to bookworm and it works now |
Beta Was this translation helpful? Give feedback.
-
|
I have some problem thread 'main' panicked at crates/gpui/src/platform/linux/x11/client.rs:376:47: Stack backtrace: I use ubuntu20.04 ,amd r7 6800H |
Beta Was this translation helpful? Give feedback.
-
|
Crashes when forced to use physical device - works only in software mode PAN_I_WANT_A_BROKEN_VULKAN_DRIVER=1 \
ENABLE_DEVICE_CHOOSER_LAYER=1 VULKAN_DEVICE_INDEX=0 \
RUST_BACKTRACE=1 RUST_LOG='blade_graphics=debug' .local/zed-preview.app/bin/zed --foreground
WARNING: panvk is not a conformant Vulkan implementation, testing use only.
Using Vulkan device index 0
[2025-03-28T10:57:10+01:00 INFO blade_graphics::hal::init] Presentation support: "VK_KHR_wayland_surface"
[2025-03-28T10:57:10+01:00 INFO blade_graphics::hal::init] Presentation support: "VK_KHR_xcb_surface"
[2025-03-28T10:57:10+01:00 INFO blade_graphics::hal::init] Presentation support: "VK_KHR_xlib_surface"
[2025-03-28T10:57:10+01:00 INFO blade_graphics::hal::init] Enabling Vulkan Portability
[2025-03-28T10:57:10+01:00 INFO blade_graphics::hal::init] Enabling color space support
[2025-03-28T10:57:10+01:00 INFO blade_graphics::hal::init] Adapter: "Mali-G52 (Panfrost)"
[2025-03-28T10:57:10+01:00 WARN blade_graphics::hal::init] Rejected for API version 4194609
thread 'main' panicked at crates/gpui/src/platform/linux/wayland/client.rs:465:47:
Unable to init GPU context: NoSupportedDeviceFound
Stack backtrace:
0: std::backtrace::Backtrace::create
1: anyhow::error::<impl anyhow::Error>::msg
2: gpui::platform::blade::blade_context::BladeContext::new
3: gpui::platform::linux::wayland::client::WaylandClient::new
4: gpui::platform::current_platform
5: gpui::app::Application::new
6: zed::main
7: std::sys::backtrace::__rust_begin_short_backtrace
8: std::rt::lang_start::{{closure}}
9: std::rt::lang_start_internal
10: main
11: <unknown>
12: __libc_start_main
13: _start
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: gpui::platform::linux::wayland::client::WaylandClient::new
4: gpui::platform::current_platform
5: gpui::app::Application::new
6: zed::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.Linux vim 6.1.79-1-MANJARO-ARM-AML |
Beta Was this translation helpful? Give feedback.
-
|
Your graphics driver is missing support for |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Check for existing issues
Describe the bug / provide steps to reproduce it
Environment
ubuntu 20.04
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your
~/Library/Logs/Zed/Zed.logfile to this issue.Zed.log
Beta Was this translation helpful? Give feedback.
All reactions