unable to run zed error info Instance extension "VK_KHR_get_physical_device_properties2" is not supported.

[getpool]

trafficstars

Check for existing issues

• [x] Completed

Describe the bug / provide steps to reproduce it

Unable to run zed Instance extension "VK_KHR_get_physical_device_properties2" is not supported

Environment

windows 11 Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz 2.20 GHz Intel HD 4600

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

Zed.log

2024-09-09T22:03:50.5059463+08:00 [INFO] ========== starting zed ==========
2024-09-09T22:03:50.6002955+08:00 [INFO] Use Microsoft YaHei UI as UI font.
2024-09-09T22:03:50.602582+08:00 [INFO] Opening main db
2024-09-09T22:03:50.6091429+08:00 [INFO] Using git binary path: None
2024-09-09T22:03:50.6108621+08:00 [ERROR] SHELL environment variable is not assigned so we can't source login environment variables
Caused by:
environment variable not found
2024-09-09T22:03:50.6115436+08:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-09-09T22:03:50.6734594+08:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-09-09T22:03:50.6739225+08:00 [INFO] initializing context server client
2024-09-09T22:03:50.6762795+08:00 [INFO] Registering built-in prompt template: content_prompt
2024-09-09T22:03:50.6769992+08:00 [INFO] Registering built-in prompt template: edit_workflow
2024-09-09T22:03:50.6774984+08:00 [INFO] Registering built-in prompt template: step_resolution
2024-09-09T22:03:50.6782872+08:00 [INFO] Registering built-in prompt template: terminal_assistant_prompt
2024-09-09T22:03:50.6789808+08:00 [INFO] No prompt template overrides directory found at C:\Users\Administrator\AppData\Local\Zed\prompt_overrides. Using built-in prompts.
2024-09-09T22:03:50.6798146+08:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-09-09T22:03:50.6944397+08:00 [INFO] Opening main db
2024-09-09T22:03:50.6985827+08:00 [ERROR] 找不到元素。 (0x80070490)
2024-09-09T22:03:50.6991336+08:00 [ERROR] Error { kind: Generic("Input watch path is neither a file nor a directory."), paths: [] }
2024-09-09T22:03:50.7143257+08:00 [ERROR] Instance extension "VK_KHR_get_physical_device_properties2" is not supported

[getpool]

HD4600 does not support Vulkan, so it will not run. very good software. i use it on another computer, but the old hardware cannot run it. can the requirements be lowered?

[github-actions[bot]]

Hi there! 👋 We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Zed, please let us know by commenting on this issue, and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 7 days. Thanks for your help!

[pablobm]

I can confirm that this is an issue at the moment. I installed Zed 20 mins ago with curl -f https://zed.dev/install.sh | sh.

$ ~/.local/bin/zed -v          
Zed 0.170.4 – /home/pablobm/.local/zed.app/libexec/zed-editor
$ RUST_BACKTRACE=full ~/.local/bin/zed --foreground
[2025-01-28T21:18:15+00:00 ERROR blade_graphics::hal::init] Instance extension "VK_KHR_get_physical_device_properties2" is not supported
thread 'main' panicked at crates/gpui/src/platform/linux/x11/client.rs:374:47:
Unable to init GPU context: NoSupportedDeviceFound

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: gpui::platform::blade::blade_context::BladeContext::new
   2: gpui::platform::linux::x11::client::X11Client::new
   3: gpui::platform::current_platform
   4: gpui::app::App::new
   5: zed::main
   6: std::sys::backtrace::__rust_begin_short_backtrace
   7: std::rt::lang_start::{{closure}}
   8: std::rt::lang_start_internal
   9: main
  10: <unknown>
  11: __libc_start_main
  12: _start
stack backtrace:
   0:     0x55cc394469db - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h1b9dad2a88e955ff
   1:     0x55cc35c489ab - core::fmt::write::h4b5a1270214bc4a7
   2:     0x55cc39441ad3 - std::io::Write::write_fmt::hd04af345a50c312d
   3:     0x55cc3944870a - std::panicking::default_hook::{{closure}}::h96ab15e9936be7ed
   4:     0x55cc39448357 - std::panicking::default_hook::h3cacb9c27561ad33
   5:     0x55cc39448d69 - std::panicking::rust_panic_with_hook::hfe205f6954b2c97b
   6:     0x55cc39448c77 - std::panicking::begin_panic_handler::{{closure}}::h6cb44b3a50f28c44
   7:     0x55cc39446ea9 - std::sys::backtrace::__rust_end_short_backtrace::hf1c1f2a92799bb0e
   8:     0x55cc39448904 - rust_begin_unwind
   9:     0x55cc347680b3 - core::panicking::panic_fmt::h3d8fc78294164da7
  10:     0x55cc34768586 - core::result::unwrap_failed::hfa79a499befff387
  11:     0x55cc37134157 - gpui::platform::linux::x11::client::X11Client::new::h7ef2bb761aae1d17
  12:     0x55cc3715f5d4 - gpui::platform::current_platform::hc78bf02b4aa8378a
  13:     0x55cc3708c742 - gpui::app::App::new::hcf2b581b6af4ec1d
  14:     0x55cc3aa2c6e4 - zed::main::h7d15a402f4834203
  15:     0x55cc3aa94283 - std::sys::backtrace::__rust_begin_short_backtrace::h15a09efa9bc79fab
  16:     0x55cc3ab5c3d9 - std::rt::lang_start::{{closure}}::hff6b547331ce15b8
  17:     0x55cc39436985 - std::rt::lang_start_internal::h5e7c81cecd7f0954
  18:     0x55cc3aa307dc - main
  19:     0x7f1735e4624a - <unknown>
  20:     0x7f1735e46305 - __libc_start_main
  21:     0x55cc34aa727e - _start
  22:                0x0 - <unknown>

I run Debian GNU/Linux 12 (bookworm) on a Thinkpad T480s. Some additional details:

$ lscpu    
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          39 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   8
  On-line CPU(s) list:    0-7
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    CPU family:           6
    Model:                142
    Thread(s) per core:   2
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             10
    CPU(s) scaling MHz:   24%
    CPU max MHz:          3400.0000
    CPU min MHz:          400.0000
    BogoMIPS:             3600.00
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc ar
                          t arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4
                          _1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_sha
                          dow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust sgx bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsave
                          s dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
Virtualization features:  
  Virtualization:         VT-x
Caches (sum of all):      
  L1d:                    128 KiB (4 instances)
  L1i:                    128 KiB (4 instances)
  L2:                     1 MiB (4 instances)
  L3:                     6 MiB (1 instance)
NUMA:                     
  NUMA node(s):           1
  NUMA node0 CPU(s):      0-7
Vulnerabilities:          
  Gather data sampling:   Vulnerable: No microcode
  Itlb multihit:          KVM: Mitigation: VMX disabled
  L1tf:                   Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
  Mds:                    Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:               Mitigation; PTI
  Mmio stale data:        Mitigation; Clear CPU buffers; SMT vulnerable
  Reg file data sampling: Not affected
  Retbleed:               Mitigation; IBRS
  Spec rstack overflow:   Not affected
  Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:             Mitigation; IBRS; IBPB conditional; STIBP conditional; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                  Mitigation; Microcode
  Tsx async abort:        Not affected

[OnorioCatenacci]

FWIW, I don't see this issue on either Windows 11 or Ubuntu so I think it can be closed. But I don't have Intel HD4600 so that might have some bearing on this.

Win 11 -- Zed Dev 0.188.0 Ubuntu -- Zed 0.186.9

[pablobm]

Unfortunately still an issue for me:

$ zed -v                              
Zed 0.187.9 377a9b61b861a374fac85265f1265ea9f9f95631  – /home/pablobm/.local/zed.app/libexec/zed-editor
$ RUST_BACKTRACE=full zed --foreground
2025-05-28T14:49:25+01:00 INFO  [zed] ========== starting zed ==========
2025-05-28T14:49:25+01:00 INFO  [gpui::platform::linux::x11::client] Compositor detection: _NET_WM_CM_S?=false, _NET_WM_CM_OWNER=false, _NET_SUPPORTING_WM_CHECK=true
2025-05-28T14:49:25+01:00 INFO  [gpui::platform::linux::x11::client] x11: compositor present: true, gtk_frame_extents_supported: true
2025-05-28T14:49:29+01:00 ERROR [blade_graphics::hal::init] Instance extension "VK_KHR_get_physical_device_properties2" is not supported

thread 'main' panicked at crates/gpui/src/platform/linux/x11/client.rs:377:47:
Unable to init GPU context: NoSupportedDeviceFound

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: gpui::platform::blade::blade_context::BladeContext::new
   2: gpui::platform::linux::x11::client::X11Client::new
   3: gpui::platform::current_platform
   4: gpui::app::Application::new
   5: zed::main
   6: std::sys::backtrace::__rust_begin_short_backtrace
   7: std::rt::lang_start::{{closure}}
   8: std::rt::lang_start_internal
   9: main
  10: <unknown>
  11: __libc_start_main
  12: _start
stack backtrace:
   0:     0x55e0fe78be40 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h6d42cc84fc840290
   1:     0x55e0f99e9133 - core::fmt::write::h5af61a909e3ec64d
   2:     0x55e0fe786463 - std::io::Write::write_fmt::h5a7b54aa6e4a315d
   3:     0x55e0fe78bca2 - std::sys::backtrace::BacktraceLock::print::h555579e7396c26ac
   4:     0x55e0fe78d49e - std::panicking::default_hook::{{closure}}::h9128866118196224
   5:     0x55e0fe78d338 - std::panicking::default_hook::h52e9e7314e0255f6
   6:     0x55e0fe78deb2 - std::panicking::rust_panic_with_hook::h541791bcc774ef34
   7:     0x55e0fe78dc7a - std::panicking::begin_panic_handler::{{closure}}::h6479a2f0137c7d19
   8:     0x55e0fe78c329 - std::sys::backtrace::__rust_end_short_backtrace::ha04e7c0fc61ded91
   9:     0x55e0fe78d91d - rust_begin_unwind
  10:     0x55e0f7b41ef0 - core::panicking::panic_fmt::h5764ee7030b7a73d
  11:     0x55e0f7b42326 - core::result::unwrap_failed::h3ff7104a9ace307a
  12:     0x55e0fb69369b - gpui::platform::linux::x11::client::X11Client::new::h03fb199ffdb68f8e
  13:     0x55e0fb6c1eb7 - gpui::platform::current_platform::hcad75b1649d58c26
  14:     0x55e0fb5d2df2 - gpui::app::Application::new::he7bda882bc1d3a6f
  15:     0x55e10020819d - zed::main::ha4460f18a37b3b4d
  16:     0x55e1001752a3 - std::sys::backtrace::__rust_begin_short_backtrace::hc5f95386b864f23d
  17:     0x55e10019ff19 - std::rt::lang_start::{{closure}}::h350d4978572fada2
  18:     0x55e0fe77b5a1 - std::rt::lang_start_internal::h15895544e2012228
  19:     0x55e10020dbfc - main
  20:     0x7f94590a724a - <unknown>
  21:     0x7f94590a7305 - __libc_start_main
  22:     0x55e0f7d8cf4e - _start
  23:                0x0 - <unknown>

Same machine as described in previous comment. Packages up to date.

[dyrnq]

stare

[dyrnq]

@pablobm hello,whitch distribution linux are you using.

as https://zed.dev/docs/system-requirements#linux says Zed requires a Vulkan 1.3 driver

I use debian12 and CPU is Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz

if you are using debian the same, you can flow this steps:

dpkg --add-architecture i386
apt update
apt install mesa-vulkan-drivers libglx-mesa0:i386 mesa-vulkan-drivers:i386 libgl1-mesa-dri:i386 -y

xref https://github.com/lutris/docs/issues/134

[OnorioCatenacci]

@pablobm Are you attempting to run via WSL? I'm asking because I see the $ prompt there. If you are attempting to run under WSL that may be part of the issue and you should add that detail to the original bug report. Windows isn't officially supported yet and I'm willing to guess that using WSL on Windows is even less likely to work as expected but that's just my guess.

[pablobm]

@dyrnq - Thank you, that worked! My bad for not reading that, then. Although I have to admit that stuff is a bit esoteric for me 😳

@OnorioCatenacci - No, it's a "real" Debian machine 👍

Anyway, as far as I'm concerned this works now 😄 Thank you team.

[OnorioCatenacci]

Ok so you never saw a problem on a Windows machine then @pablobm? So it seems this issue is no longer present on a Windows machine (at least with Zed Dev 0.188.0). I'd say this can be closed unless @getpool can test it and post if the issue still occurs.

[pablobm]

@OnorioCatenacci - Correct. I haven't touched a Windows machine in a while.

[sppfly]

I met this issue as well on Opensuse Leap 15.6, exactly the same error

[OnorioCatenacci]

This was originally reported on Windows. If you're seeing this error on Linux a separate bug should be created because the differences between Linux and Windows are non-trivial. I see other errors reported for this on Linux. You should look at those; this is the wrong place to report an error on Linux.

[vagra]

Windows 10 Mingw64 pacman -Ss mingw-w64-x86_64-zed: mingw64/mingw-w64-x86_64-zed 0.188.5-1

zed --foreground
2025-06-07T21:06:32+08:00 INFO  [zed] ========== starting zed ==========
2025-06-07T21:06:33+08:00 INFO  [gpui::platform::windows::direct_write] Use Microsoft YaHei UI as UI
 font.
2025-06-07T21:06:33+08:00 INFO  [blade_graphics::hal::init] Presentation support: "VK_KHR_win32_surf
ace"
2025-06-07T21:06:33+08:00 INFO  [blade_graphics::hal::init] Enabling Vulkan Portability
2025-06-07T21:06:33+08:00 INFO  [blade_graphics::hal::init] Enabling color space support
2025-06-07T21:06:33+08:00 INFO  [blade_graphics::hal::init] Adapter: "GeForce GTX 650"
2025-06-07T21:06:33+08:00 WARN  [blade_graphics::hal::init] Rejected for device extension "VK_KHR_dy
namic_rendering" not supported. Please update the driver!

thread 'main' panicked at crates\gpui\src\platform\windows\platform.rs:109:47:
Unable to init GPU context: NoSupportedDeviceFound
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[neviaumi]

I am encountering an issue with Zed on a fresh installation of EndeavourOS (Arch-based Linux) on my 2016 15-inch MacBook Pro.

I followed the standard installation instructions from the official Zed documentation and ran the required commands.

After the setup, when I attempted to launch Zed, it failed to start and produced the following error.

---

Steps to Reproduce

1. Perform a fresh installation of EndeavourOS on a 2016 15-inch MacBook Pro.
2. Follow the standard Zed installation instructions.
3. Run the command RUST_BACKTRACE=full zed --foreground in the terminal.

Expected Behavior

I expected the Zed editor to launch successfully.

Actual Behavior

The editor did not launch, and the following error was displayed:

Click to view full error log

2025-09-05T18:56:55+01:00 INFO  [zed] ========== starting zed version 0.202.7, sha cd9b0b5 ==========
2025-09-05T18:56:55+01:00 ERROR [blade_graphics::hal::init] Instance extension "VK_KHR_get_physical_device_properties2" is not supported

thread 'main' panicked at crates/gpui/src/platform/linux/wayland/client.rs:500:47:
Unable to init GPU context: NoSupportedDeviceFound

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: anyhow::__private::format_err
   2: gpui::platform::blade::blade_context::BladeContext::new::{{closure}}
   3: gpui::platform::blade::blade_context::BladeContext::new
   4: gpui::platform::linux::wayland::client::WaylandClient::new
   5: gpui::platform::current_platform
   6: gpui::app::Application::new
   7: zed::main
   8: std::sys::backtrace::__rust_begin_short_backtrace
   9: std::rt::lang_start::{{closure}}
  10: std::rt::lang_start_internal
  11: main
  12: <unknown>
  13: __libc_start_main
  14: _start
stack backtrace:
   0:     0x562198e04503 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hf435e8e9347709a8
   1:     0x5621930d89c3 - core::fmt::write::h0a51fad3804c5e7c
   2:     0x562198dfec63 - std::io::Write::write_fmt::h9759e4151bf4a45e
   3:     0x562198e04362 - std::sys::backtrace::BacktraceLock::print::h1ec5ce5bb8ee285e
   4:     0x562198e0825a - std::panicking::default_hook::{{closure}}::h5ffefe997a3c75e4
   5:     0x562198e07dfa - std::panicking::default_hook::h820c77ba0601d6bb
   6:     0x562198e08992 - std::panicking::rust_panic_with_hook::h8b29cbe181d50030
   7:     0x562198e0875a - std::panicking::begin_panic_handler::{{closure}}::h9f5b6f6dc6fde83e
   8:     0x562198e049d9 - std::sys::backtrace::__rust_end_short_backtrace::hd7b0c344383b0b61
   9:     0x562198e0840d - __rustc[5224e6b81cd82a8f]::rust_begin_unwind
  10:     0x56219066f6c0 - core::panicking::panic_fmt::hc49fc28484033487
  11:     0x56219066fae6 - core::result::unwrap_failed::h9e4c136384b1cfa3
  12:     0x56219522c7cf - gpui::platform::linux::wayland::client::WaylandClient::new::hde82587842a3a137
  13:     0x56219528cafd - gpui::platform::current_platform::h2efa4456c04c493e
  14:     0x562195194a60 - gpui::app::Application::new::h2da523636da657d8
  15:     0x56219aa2e70c - zed::main::he41ed464eac4e32a
  16:     0x56219abe7af3 - std::sys::backtrace::__rust_begin_short_backtrace::h7d3fd0502852abc0
  17:     0x56219abe7ad9 - std::rt::lang_start::{{closure}}::he59b8b18050fc684
  18:     0x562198df3ae1 - std::rt::lang_start_internal::h31bbb7f936fd6b5d
  19:     0x56219abe7b3c - main
  20:     0x7ff9ff027675 - <unknown>
  21:     0x7ff9ff027729 - __libc_start_main
  22:     0x56219095d26e - _start
  23:                0x0 - <unknown>

Additional Information

• Operating System: EndeavourOS (Arch-based Linux)
• Hardware: 2016 15-inch MacBook Pro
• Processor: Intel(R) Core(TM) i7-6820HQ CPI @ 2.70Ghz
• Graphics: AMD Radeon RX Graphics (radeonsi, polaris11, ACO, DRM 3.64, 6.16.4-arch1-1)
• Zed Version: 0.202.7