zed
zed copied to clipboard
zed-industries
Tracking Issue: Invisible Window on Linux
No Zed Window on Launch (Linux)
This is a tracking issue to help consolidate the many distinct issues where this has been reported in an attempt to identify the configurations and determine whether there are one or more common issues behind this.
Apologies for spam on mentioned issues and users @ mentions. Just hoping to raise visibility of potential workarounds for users still impacted by this issue.
Broken:
- Trixie (Ubuntu 24.04, Ubuntu 23.10 on WSL2)
- Bookworm (Ubuntu 20.04, Ubuntu 22.04, Ubuntu 22.04 on WSL2, Mint 20.3, Mint, Mint 21.2, Mint 21.3, Pop!_OS 22.04, Debian 12.5, LMDE6)
- RedHat (RHEL 9.4, RHEL 9.3, Rocky 9.3, Fedora 39)
- Arch (Arch 2024.07.01, Arch on WSL2, EndevourOS, Manjaro)
- NixOS
Fixed:
-
"When I boot Ubuntu 24.04 on the same device, Zed works." (@eyelash comment on #14204)
-
"for anyone wanna run zed on WSL Ubuntu 22.04:" (@0x5ea000000 comment on #14126).
sudo apt-get install libvulkan-dev sudo add-apt-repository ppa:kisak/kisak-mesa sudo apt update && sudo apt upgrade WAYLAND_DISPLAY='' zed --foreground -
"Ryzen APU with Linux Mint 20.3, it worked after installing mesa-vulkan-drivers from Kisak's PPA. (@definitelyuncertain comment on #14204
sudo add-apt-repository ppa:kisak/kisak-mesa sudo apt update && sudo apt upgrade -
"Works fine after force the app running with X11
env -u WAYLAND_DISPLAY zed(on Arch)" (@akbarhmu comment on #14204) -
"I managed to fixed it by updating mesa driver through kisak ppa and use liquorix kernel." (@kanowfy comment on #14173
sudo add-apt-repository ppa:damentz/liquorix sudo add-apt-repository ppa:kisak/kisak-mesa sudo apt update && sudo apt upgrade -
"Arch WSL2. rebuild mesa described like here https://github.com/microsoft/wslg/issues/1254 After that
unset WAYLAND_DISPLAY; zedworked." (@jackysee comment on #14126) and detailed instructions in this comment -
"I think this is just a Wayland in WSLg thing. However, if I run weston -B x11 to start a new compositor and run WAYLAND_DISPLAY=wayland-1 zed, it actually works" (@noah-gil comment on #14126)
-
Worked "on wsl2 upgraded to latest fedora remix version (Fedora Remix 31)" (@kelvinkwong comment on #14126)
-
Arch: "Edit: fixed by installing vulkan-intel. 👍" (@rebootl comment on #14237) and (@rebootl comment on #14237
-
"Switching my nvidia PRIME profile to "on-demand" (it was on performance mode) fixed the issue for me" (@vblanton comment on 14237)
Leads:
-
"I just did a git bisect, and the x11 gui broke in commit https://github.com/zed-industries/zed/commit/47aa761ca9dee79852056897090480ff7f5ba7a9" (@ChrisJefferson comment on #14126
-
"your driver doesn't support KHR_DYNAMIC_RENDERING which from Vulkan 1.3 and needed for Blade" (@stalkerg comment on 14237)
-
"Okey, ANV Intel driver start support it in 2022 link it should be part of ANV (Skylake and upper) and hasvk (haswell, brodwell)" (@stalkerg comment on 14237)
-
"20.04 will work only if you replace kernel and mesa drivers, which difficult." (@stalkerg comment on #14204)
-
https://github.com/zed-industries/zed/pull/14511
CPUs/GPUs
- Adapter "llvmpipe (LLVM 15.0.7, 256 bits)"
- Intel: HD Graphics (630), UHD Graphics (620, CML GT2)
- AMD Ryzen APU
- Nvidia:
- GeForce 410m (@MEHREGANKBI in #14648)
- GeForce GT 730 (@hzheboldov in issue #15608)
- GeForce GTX 1660 (@IWhitebird comment on 14126)
- GeForce GTX 1650 (@AshutoshSajan comment on #14237, @marcbrevoort-cyberhive issue 14956, @Nikita0x in issue #15631)
- GeForce RTX 2060 SUPER (@ comment on #14237)
- GeForce RTX 3070 Laptop (@vblanton comment on #14237)
- GeForce RTX 4090 (@RickyWanga comment on 14805)
Potentially Related Issues:
- https://github.com/zed-industries/zed/issues/14126#issuecomment-2221997278
- https://github.com/zed-industries/zed/issues/14173#issuecomment-2229991737
- https://github.com/zed-industries/zed/issues/14204
- https://github.com/zed-industries/zed/issues/14237
- https://github.com/zed-industries/zed/issues/14271
- https://github.com/zed-industries/zed/issues/14314
- https://github.com/zed-industries/zed/issues/14430
- https://github.com/zed-industries/zed/issues/14648
- https://github.com/zed-industries/zed/issues/14805
- https://github.com/zed-industries/zed/issues/14956
- https://github.com/zed-industries/zed/issues/15402
- https://github.com/zed-industries/zed/issues/15608
- https://github.com/zed-industries/zed/issues/15631
- https://github.com/zed-industries/zed/issues/15673
- https://github.com/zed-industries/zed/issues/15851
- https://github.com/zed-industries/zed/issues/16414
I've read every comment in each of these issue and here is my current takeaways.
- Ubuntu:
- Ideally upgrade to Ubuntu 24
- Ubuntu 20, Ubuntu 22, MintOS 20/21/22: Consider
sudo apt-get install libvulkan-dev sudo add-apt-repository ppa:kisak/kisak-mesa sudo apt update && sudo apt upgrade - Ubuntu on WSL2: Consider above + forcing running under X11 instead of wayland:
WAYLAND_DISPLAY='' zed --foreground
- Pop!_OS 22.04: Please try Pop!_OS 24.04 LTS alpha and report back.
- Arch:
- Arch with Intel Graphics:
pacman -S vulkan-intel - Arch on WSL2: Consider trying detailed instructions from @da-moon based on these instructions by @jackysee.
- Arch with Intel Graphics:
- Redhat: TBD
- NixOS: TBD
Still working on identifying solutions for users without a Vulkan-supported GPU (e.g. no modern Intel Graphics, AMD GPU, AMD APU or Nvidia GPU, etc) who are trying to use the llvmpipe software emulation and encounter this issue.
If Zed could detect the situation where the Vulkan drivers don't support Vulkan 1.3 and print a message along the lines of "please update your drivers/OS" instead of silently not opening a window, that would probably go a long way in terms of user experience.
Honestly, I prefer also to drop X11 support. Ubuntu 20.04/22.04 is the transition period (X11->Wayland), which provides many more questions and issues. 20.04/22.04 is also a transition for Vulkan support. Because Zed is still alpha or beta, I think it should be relatively safe.
I've read every comment in each of these issue and here is my current takeaways.
Ubuntu:
- Ideally upgrade to Ubuntu 24
- Ubuntu 20, Ubuntu 22, MintOS 20/21/22: Consider
sudo apt-get install libvulkan-dev sudo add-apt-repository ppa:kisak/kisak-mesa sudo apt update && sudo apt upgrade- Ubuntu on WSL2: Consider above + forcing running under X11 instead of wayland:
WAYLAND_DISPLAY='' zed --foregroundPop!_OS 22.04: Please try Pop!_OS 24.04 LTS alpha and report back.
Arch:
- Arch with Intel Graphics:
pacman -S vulkan-intel- Arch on WSL2: Consider trying these instructions
Redhat: TBD
NixOS: TBD
Still working on identifying solutions for users without a Vulkan-supported GPU (e.g. no modern Intel Graphics, AMD GPU, AMD APU or Nvidia GPU, etc) who are trying to use the
llvmpipesoftware emulation and encounter this issue.
After sudo apt-get install mesa-vulkan-drivers vulkan-tools I can run vkcube and Zed using WAYLAND_DISPLAY='' zed --foreground. I did not have to add the kisak-mesa ppa. Since I'm (forced to be) on WSL2 (Ubuntu 24.04) it uses llvmpipe and performance is nowhere near what it's like on my MacBook, for obvious reasons.
This may be related but WGPU also behaves oddly for me, giving me the error Surface does not support the adapter's queue family. Unsetting WAYLAND_DISPLAY fixes the issue. below is my neofetch:
-` draconium@DRC-FW16
.o+` ------------------
`ooo/ OS: Arch Linux x86_64
`+oooo: Host: Laptop 16 (AMD Ryzen 7040 Series) A7
`+oooooo: Kernel: 6.10.6-arch1-1
-+oooooo+: Uptime: 10 hours, 19 mins
`/:-:++oooo+: Packages: 1568 (pacman), 53 (flatpak)
`/++++/+++++++: Shell: zsh 5.9
`/++++++++++++++: Resolution: 2560x1600
`/+++ooooooooooooo/` DE: Plasma 6.1.4
./ooosssso++osssssso+` Terminal: yakuake
.oossssso-````/ossssss+` CPU: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16) @ 5.137GHz
-osssssso. :ssssssso. GPU: AMD ATI Phoenix1
:osssssss/ osssso+++. Memory: 13683MiB / 27868MiB
/ossssssss/ +ssssooo/-
`/ossssso+/:- -:/+osssso+-
`+sso+:-` `.-/+oso:
`++:. `-/+/
.` `/
Using fedora with wyland it didn't open, so change to ea X11 and it opened normally, I guess it's incompatibility with wyland, just change and that's it.
A very simple solution, be careful not to depend on some wayland feature.
So, I have an AMD Radeon integrated graphics as well as NVIDIA RTX 3060 Laptop GPU, and under WSL-2 (Ubuntu 24) I was able to get vkcube to recognize my nvidia gpu by installing kisak-mesa and liquorix kernel.
However, Zed does not pick the correct GPU - it picks llvmpipe when there are two other GPUs that are available. My guess is because the api versions for the two are 1.2, rather than 1.3. I'm not sure why 1.2 is only supported for my GPUs only under WSL-2.
Vulkaninfo gives me these 3 GPUs:
GPU0:
apiVersion = 1.2.289
driverVersion = 24.2.3
vendorID = 0x10de
deviceID = 0x2520
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = Microsoft Direct3D12 (NVIDIA GeForce RTX 3060 Laptop GPU)
driverID = DRIVER_ID_MESA_DOZEN
driverName = Dozen
driverInfo = Mesa 24.2.3 - kisak-mesa PPA
conformanceVersion = 0.0.0.0
deviceUUID = abd52523-22df-9a9a-4448-6dd05cfebe81
driverUUID = 6ee2028a-2063-39d1-a78b-ff50217faeb8
GPU1:
apiVersion = 1.2.289
driverVersion = 24.2.3
vendorID = 0x1002
deviceID = 0x1636
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Microsoft Direct3D12 (AMD Radeon(TM) Graphics)
driverID = DRIVER_ID_MESA_DOZEN
driverName = Dozen
driverInfo = Mesa 24.2.3 - kisak-mesa PPA
conformanceVersion = 0.0.0.0
deviceUUID = 7e26c875-6315-f8d1-9939-81a6392cab84
driverUUID = 6ee2028a-2063-39d1-a78b-ff50217faeb8
GPU2:
apiVersion = 1.3.289
driverVersion = 0.0.1
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 17.0.6, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 24.2.3 - kisak-mesa PPA (LLVM 17.0.6)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3234-2e32-2e33-202d206b6900
driverUUID = 6c6c766d-7069-7065-5555-494400000000
glxinfo -B seems to show that the AMD integrated GPU is the default selected:
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
WARNING: Some incorrect rendering might occur because the selected Vulkan device (Microsoft Direct3D12 (NVIDIA GeForce RTX 3060 Laptop GPU)) doesn't support base Zink requirements: feats.features.logicOp have_EXT_custom_border_color have_EXT_line_rasterization
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Microsoft Corporation (0xffffffff)
Device: D3D12 (AMD Radeon(TM) Graphics) (0xffffffff)
Version: 24.2.3
Accelerated: yes
Video memory: 8390MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.2
Max compat profile version: 4.2
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Microsoft Corporation
OpenGL renderer string: D3D12 (AMD Radeon(TM) Graphics)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 24.2.3 - kisak-mesa PPA
OpenGL core profile shading language version string: 4.20
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.2 (Compatibility Profile) Mesa 24.2.3 - kisak-mesa PPA
OpenGL shading language version string: 4.20
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 24.2.3 - kisak-mesa PPA
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
And vkcube seems to use the nvidia GPU:
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
Selected GPU 0: Microsoft Direct3D12 (NVIDIA GeForce RTX 3060 Laptop GPU), type: DiscreteGpu
And here's Zed giving me an unsupported GPU dialog:
Having basically the exact same issue as clseibold, same resulting error popup. Thou running WSL2 22.04.3 LTS (Jammy Jellyfish) on WSL2:
wsl --version
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4460
>vulkaninfo --summary
....
Devices:
========
GPU0:
apiVersion = 4202785 (1.2.289)
driverVersion = 100671495 (0x6002007)
vendorID = 0x8086
deviceID = 0xa7a1
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Microsoft Direct3D12 (Intel(R) Iris(R) Xe Graphics)
driverID = UNKNOWN_VkDriverId_value23
driverName = Dozen
driverInfo = Mesa 24.2.7 - kisak-mesa PPA
conformanceVersion = 0.0.0.0
deviceUUID = 8f0baa7a-2dea-957d-d331-6bdc89d841fa
driverUUID = a89763fc-a21b-5517-2a44-091e0c0011ae
GPU1:
apiVersion = 4206881 (1.3.289)
driverVersion = 1 (0x0001)
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 15.0.7, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 24.2.7 - kisak-mesa PPA (LLVM 15.0.7)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3234-2e32-2e37-202d206b6900
driverUUID = 6c6c766d-7069-7065-5555-494400000000
❯ vkcube
WARNING: dzn is not a conformant Vulkan implementation, testing use only.
Selected GPU 0: Microsoft Direct3D12 (Intel(R) Iris(R) Xe Graphics), type: 1
@notpeter, here's another potential one:
- https://github.com/zed-industries/zed/issues/21001
I just ran into this on a 2024 Asus G14 (AMD Integrated, NVIDIA Discrete) running Nobara (basically Fedora) when doing either DRI_PRIME=1 zed or DRI_PRIME=1 WAYLAND_DISPLAY='' zed. Just running Zed works, but it is super slow and laggy. VKCube and all that are working fine.
I can still reproduce this problem using Artix Linux with Nvidia GTX 760 and official 470xx drivers. vkcube is working fine. Zed doesn't crash neither, the profess continue fine, but window doesn't appears. Using Xorg as well.
I was using zed 100%, until i open NVIDIA Server X Settings (Ubuntu 24.04 LTS) and i changed the prime profile from "NVIDIA On-Demand" to "NVIDIA (PERFORMANCE MODE)", this issue appeared until i restore it to "NVIDIA On-Demand", and now it back and works great.
official 470xx drivers
@ryukinix too old for Zed, see https://github.com/zed-industries/zed/issues/14314#issuecomment-2295318647
official 470xx drivers
@ryukinix too old for Zed, see https://github.com/zed-industries/zed/issues/14314#issuecomment-2295318647
Thank you for pointing out the real issue around this problem in my case!
Has anyone got zed to work on debian?
Keep getting the same issues..
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
[2024-12-27T04:20:01+01:00 INFO blade_graphics::hal::init] Adapter: "Intel(R) HD Graphics 4000 (IVB GT2)"
[2024-12-27T04:20:01+01:00 WARN blade_graphics::hal::init] Rejected for device extension "VK_KHR_dynamic_rendering" not supported. Please update the driver!
[2024-12-27T04:20:01+01:00 INFO blade_graphics::hal::init] Adapter: "llvmpipe (LLVM 11.0.1, 256 bits)"
[2024-12-27T04:20:01+01:00 WARN blade_graphics::hal::init] Rejected for API version 4194306
error opening [PathWithPosition { path: "/tmp/l", row: None, column: None }]: NoSupportedDeviceFound
Has anyone got zed to work on debian?
Keep getting the same issues..
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete [2024-12-27T04:20:01+01:00 INFO blade_graphics::hal::init] Adapter: "Intel(R) HD Graphics 4000 (IVB GT2)" [2024-12-27T04:20:01+01:00 WARN blade_graphics::hal::init] Rejected for device extension "VK_KHR_dynamic_rendering" not supported. Please update the driver! [2024-12-27T04:20:01+01:00 INFO blade_graphics::hal::init] Adapter: "llvmpipe (LLVM 11.0.1, 256 bits)" [2024-12-27T04:20:01+01:00 WARN blade_graphics::hal::init] Rejected for API version 4194306 error opening [PathWithPosition { path: "/tmp/l", row: None, column: None }]: NoSupportedDeviceFound
try to see this: https://www.reddit.com/r/linux_gaming/comments/proo87/mesaintel_warning_ivy_bridge_vulkan_support_is/
@flipchan
Also, please share your hardware info as well, and please check if your drivers are up to date.
Zed requires a Vulkan compatible GPU, Vulkan 1.3 driver, and the following desktop portals:
org.freedesktop.portal.FileChooser
org.freedesktop.portal.OpenURI
org.freedesktop.portal.Secret, or org.freedesktop.Secrets
glibc version >= 2.35 is recommended.
To make sure you have vulkan driver installed, can you please try vulkaninfo on your terminal?
Also please try
vkcube --gpu_number 0
and
vkcube --gpu_number 1
In case everything is configured properly, both the commands should open up a window with a rotating cube on the display.
@clseibold
Can you please try manually switching to your NVIDIA GPU?
sudo prime-select nvidia
I just ran into this on a 2024 Asus G14 (AMD Integrated, NVIDIA Discrete) running Nobara (basically Fedora) when doing either
DRI_PRIME=1 zedorDRI_PRIME=1 WAYLAND_DISPLAY='' zed. Just running Zed works, but it is super slow and laggy. VKCube and all that are working fine.
I need to use DRI_PRIME=1 on NixOS Budgie (X11) to be able to use Zed, when it starts it's a mess, sometimes I need to guess where the window is, but when I put it fullscreen and back to windowed it works great. My issue: (22288)[https://github.com/zed-industries/zed/issues/22288]
Having the same issue on OpenSuse 15.6 both with curl installation and using editors repo.
I have nvidia selected with prime-select and glxspheres utilize Nvidia driver:
glxspheres
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
GLX FB config ID of window: 0xad (8/8/8/0)
Visual ID of window: 0x27
Context is Direct
OpenGL Renderer: NVIDIA GeForce RTX 4090 Laptop GPU/PCIe/SSE2
240.325441 frames/sec - 268.203193 Mpixels/sec
239.987984 frames/sec - 267.826590 Mpixels/sec
Zed Log:
2025-01-17T12:26:00.290434552Z [INFO] ========== starting zed ==========
2025-01-17T12:26:00.300674111Z [WARN] Failed to load a font face 0 from '/usr/share/fonts/texlive-helmholtz-ellis-ji-notation/HEJI2Text.otf' cause font doesn't have a family name.
2025-01-17T12:26:00.310971994Z [WARN] failed to load font 'FandolBraille-Display'
2025-01-17T12:26:00.31120427Z [WARN] failed to load font 'FandolBraille-Regular'
2025-01-17T12:26:00.313364256Z [WARN] failed to load font 'FandolBraille-Display'
2025-01-17T12:26:00.313377891Z [WARN] failed to load font 'FandolBraille-Regular'
2025-01-17T12:26:00.314294393Z [INFO] Compositor detection: _NET_WM_CM_S?=false, _NET_WM_CM_OWNER=false, _NET_SUPPORTING_WM_CHECK=true
2025-01-17T12:26:00.314310025Z [INFO] x11: compositor present: true, gtk_frame_extents_supported: true
2025-01-17T12:26:00.315949882Z [INFO] Try connect ibus
2025-01-17T12:26:00.316283666Z [INFO] perform;
2025-01-17T12:26:00.316324913Z [INFO] authenticate;
2025-01-17T12:26:00.316333793Z [INFO] Opening main db
2025-01-17T12:26:00.316354705Z [INFO] read_command;
2025-01-17T12:26:00.31670673Z [INFO] new;
2025-01-17T12:26:00.316714287Z [INFO] socket reader;
2025-01-17T12:26:00.316858457Z [INFO] Opening main db
2025-01-17T12:26:00.317387953Z [INFO] keep_updated;
2025-01-17T12:26:00.317679712Z [INFO] Using git binary path: None
2025-01-17T12:26:00.334039048Z [INFO] set environment variables from shell:/bin/bash, path:/usr/lib64/jvm/java-20-openjdk-20/bin:/home/user/.local/bin:/usr/local/bin:/usr/bin:/bin:/home/user/Android/sdk/emulator:/home/user/Android/sdk/platform-tools:/home/user/Android/sdk/emulator:/home/user/Android/sdk/platform-tools
2025-01-17T12:26:00.338507313Z [ERROR] No such file or directory (os error 2) about ["/home/user/.config/github-copilot"]
2025-01-17T12:26:00.338851183Z [INFO] No prompt template overrides directory found at /home/user/.local/share/zed/prompt_overrides. Using built-in prompts.
2025-01-17T12:26:00.340069476Z [INFO] activate is not implemented on Linux, ignoring the call
2025-01-17T12:26:00.341001292Z [INFO] Opening main db
2025-01-17T12:26:00.341399558Z [INFO] perform;
2025-01-17T12:26:00.341414579Z [INFO] authenticate;
2025-01-17T12:26:00.341432525Z [INFO] read_command;
2025-01-17T12:26:00.3419175Z [INFO] socket reader;
2025-01-17T12:26:00.342877265Z [INFO] installing extension html latest version
2025-01-17T12:26:00.343122796Z [INFO] Using Visual { id: 35, colormap: 0, depth: 32 }
2025-01-17T12:26:00.343133451Z [INFO] Creating colormap 63963139
2025-01-17T12:26:00.358026401Z [INFO] Enabling Vulkan Portability
2025-01-17T12:26:00.358039668Z [INFO] Enabling color space support
2025-01-17T12:26:00.36960182Z [INFO] Adapter: "Intel(R) Graphics (RPL-S)"
2025-01-17T12:26:00.369822677Z [INFO] No ray tracing extensions are supported
2025-01-17T12:26:00.371287793Z [INFO] Using surface present mode MAILBOX
2025-01-17T12:26:00.371312244Z [WARN] Unable to forbid exclusive full screen
2025-01-17T12:26:00.384497241Z [INFO] Creating a descriptor pool for at most 16 sets
2025-01-17T12:26:00.384525226Z [INFO] Creating a descriptor pool for at most 16 sets
2025-01-17T12:26:00.384542062Z [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: Ignored }
2025-01-17T12:26:00.396431179Z [INFO] Refreshing at 4166 micros
2025-01-17T12:26:00.396974742Z [INFO] Using GPU: GPUSpecs { is_software_emulated: false, device_name: "Intel(R) Graphics (RPL-S)", driver_name: "Intel open-source Mesa driver", driver_info: "Mesa 23.3.4" }
2025-01-17T12:26:00.42201158Z [INFO] Opening main db
2025-01-17T12:26:00.422826091Z [INFO] Opening main db
Starting the editor adding DRI_PRIME=1 in the beginning works for me:
DRI_PRIME=1 /usr/bin/zed
Here to add my own datum to the pile:
Manjaro 25.0.0 Hyprland 0.48.0 Zed 0.179.2
2025-04-08T15:41:12.37700181-07:00 [INFO] Using GPU: GpuSpecs { is_software_
│ emulated: false, device_name: "AMD Radeon RX 6700 XT (RADV NAVI22)", driver_
│ name: "radv", driver_info: "Mesa 25.0.2-arch1.2" }
The fix that finally worked for me was the run it from the command line after WAYLAND_DISPLAY=''.
While I tried a bunch of installing, reinstalling, flatpak, rebooting... This seems to be the only thing that mattered.
I'm having issues with running Zed in a WSL Debian environment, as I wrote in the issue #28418.
Running vulkaninfo --summary gives me the following output
GPU0:
apiVersion = 1.3.230
driverVersion = 0.0.1
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 15.0.6, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 22.3.6 (LLVM 15.0.6)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3232-2e33-2e36-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
The vkcube command works properly
I've added the following two lines in my .bashrc file
export ZED_ALLOW_EMULATED_GPU=1
alias zed="WAYLAND_DISPLAY='' zed"
Here are the logs from my latest launch
2025-04-09T18:17:08.26959355+02:00 [INFO] ========== starting zed ==========
2025-04-09T18:17:08.281615338+02:00 [INFO] Compositor detection: _NET_WM_CM_S?=false, _NET_WM_CM_OWNER=false, _NET_SUPPORTING_WM_CHECK=true
2025-04-09T18:17:08.281945448+02:00 [INFO] x11: compositor present: true, gtk_frame_extents_supported: false
2025-04-09T18:17:08.375959152+02:00 [INFO] Presentation support: "VK_KHR_wayland_surface"
2025-04-09T18:17:08.376073335+02:00 [INFO] Presentation support: "VK_KHR_xcb_surface"
2025-04-09T18:17:08.376142328+02:00 [INFO] Presentation support: "VK_KHR_xlib_surface"
2025-04-09T18:17:08.376212056+02:00 [INFO] Enabling Vulkan Portability
2025-04-09T18:17:08.391354666+02:00 [INFO] Adapter: "llvmpipe (LLVM 15.0.6, 256 bits)"
2025-04-09T18:17:08.392570208+02:00 [INFO] No ray tracing extensions are supported
2025-04-09T18:17:08.414439863+02:00 [INFO] Opening main db
2025-04-09T18:17:08.417417636+02:00 [INFO] Opening main db
2025-04-09T18:17:08.423643547+02:00 [INFO] Using git binary path: None
2025-04-09T18:17:08.436619334+02:00 [INFO] set environment variables from shell:/bin/bash, path:/home/niksa/.local/bin:/home/niksa/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/Common Files/Oracle/Java/javapath:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/dotnet/:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Program Files/CodeBlocks/MinGW/bin:/mnt/c/Users/Win10/AppData/Local/Programs/Python/Python310:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files (x86)/Microsoft SQL Server/160/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/160/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/Client SDK/ODBC/170/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/160/DTS/Binn/:/mnt/c/Program Files (x86)/Microsoft SQL Server/160/DTS/Binn/:/mnt/c/Program Files/Go/bin:/mnt/c/Program Files (x86)/Windows Kits/10/Windows Performance Toolkit/:/mnt/c/Program Files/Microsoft SQL Server/150/Tools/Binn/:/mnt/c/Program Files/Docker/Docker/resources/bin:/mnt/c/Users/Win10/AppData/Local/Programs/Python/Python310/Scripts:/mnt/c/Users/Win10/AppData/Local/Programs/MiKTeX:/mnt/c/Program Files/CMake/bin:/mnt/c/sqlite:/mnt/c/Users/Win10/.cargo/bin:/mnt/c/Users/Win10/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/Win10/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/ghcup/bin:/mnt/c/Users/Win10/.dotnet/tools:/mnt/c/Users/Win10/AppData/Roaming/npm:/mnt/c/Users/Win10/go/bin:/mnt/c/Users/Win10/AppData/Local/Pandoc/:/mnt/c/Users/Win10/AppData/Local/Programs/MiKTeX/miktex/bin/x64/:/mnt/c/Users/Win10/AppData/Local/Programs/mongosh/:/mnt/c/Program Files/MongoDB/Tools/100/bin:/mnt/c/Users/Win10/AppData/Local/Programs/Python/Python310/Scripts:/mnt/c/Users/Win10/flutter/bin
2025-04-09T18:17:08.472924594+02:00 [INFO] No prompt template overrides directory found at /home/niksa/.local/share/zed/prompt_overrides. Using built-in prompts.
2025-04-09T18:17:08.474898575+02:00 [INFO] extensions updated. loading 1, reloading 0, unloading 0
2025-04-09T18:17:08.480937174+02:00 [INFO] activate is not implemented on Linux, ignoring the call
2025-04-09T18:17:10.219357063+02:00 [ERROR] auto-update failed: error:Aborting. Could not find rsync which is required for auto-updates.
2025-04-09T18:17:10.220153215+02:00 [ERROR] DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:17:10.229043317+02:00 [INFO] Opening main db
2025-04-09T18:17:10.244749089+02:00 [INFO] Using Visual { id: 73, colormap: 0, depth: 32 }
2025-04-09T18:17:10.245210317+02:00 [INFO] Creating colormap 6291459
2025-04-09T18:17:10.245401162+02:00 [INFO] considering ancestor: "/home/niksa/testfolder/.git"
2025-04-09T18:17:10.245842949+02:00 [INFO] containing git repository: None
2025-04-09T18:17:10.246704557+02:00 [INFO] scanning directory ""
2025-04-09T18:17:10.252246915+02:00 [INFO] Using surface present mode MAILBOX
2025-04-09T18:17:10.254961651+02:00 [INFO] Creating a descriptor pool for at most 16 sets
2025-04-09T18:17:10.255081217+02:00 [INFO] Creating a descriptor pool for at most 16 sets
2025-04-09T18:17:10.255164396+02:00 [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: Ignored }
2025-04-09T18:17:10.420378721+02:00 [INFO] Refreshing at 16722 micros
2025-04-09T18:17:10.420941677+02:00 [INFO] x11: no compositor present, falling back to server-side window decorations
2025-04-09T18:17:10.425427682+02:00 [INFO] Using GPU: GpuSpecs { is_software_emulated: true, device_name: "llvmpipe (LLVM 15.0.6, 256 bits)", driver_name: "llvmpipe", driver_info: "Mesa 22.3.6 (LLVM 15.0.6)" }
2025-04-09T18:17:11.952191426+02:00 [INFO] Opening main db
2025-04-09T18:17:11.992749082+02:00 [INFO] Opening main db
2025-04-09T18:17:16.969503227+02:00 [INFO] using project environment variables from CLI. PATH="/home/niksa/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/Common Files/Oracle/Java/javapath:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/dotnet/:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Program Files/CodeBlocks/MinGW/bin:/mnt/c/Users/Win10/AppData/Local/Programs/Python/Python310:/mnt/c/Program Files/Git/cmd:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files (x86)/Microsoft SQL Server/160/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/160/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/Client SDK/ODBC/170/Tools/Binn/:/mnt/c/Program Files/Microsoft SQL Server/160/DTS/Binn/:/mnt/c/Program Files (x86)/Microsoft SQL Server/160/DTS/Binn/:/mnt/c/Program Files/Go/bin:/mnt/c/Program Files (x86)/Windows Kits/10/Windows Performance Toolkit/:/mnt/c/Program Files/Microsoft SQL Server/150/Tools/Binn/:/mnt/c/Program Files/Docker/Docker/resources/bin:/mnt/c/Users/Win10/AppData/Local/Programs/Python/Python310/Scripts:/mnt/c/Users/Win10/AppData/Local/Programs/MiKTeX:/mnt/c/Program Files/CMake/bin:/mnt/c/sqlite:/mnt/c/Users/Win10/.cargo/bin:/mnt/c/Users/Win10/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/Win10/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/ghcup/bin:/mnt/c/Users/Win10/.dotnet/tools:/mnt/c/Users/Win10/AppData/Roaming/npm:/mnt/c/Users/Win10/go/bin:/mnt/c/Users/Win10/AppData/Local/Pandoc/:/mnt/c/Users/Win10/AppData/Local/Programs/MiKTeX/miktex/bin/x64/:/mnt/c/Users/Win10/AppData/Local/Programs/mongosh/:/mnt/c/Program Files/MongoDB/Tools/100/bin:/mnt/c/Users/Win10/AppData/Local/Programs/Python/Python310/Scripts:/mnt/c/Users/Win10/flutter/bin"
2025-04-09T18:17:17.626442841+02:00 [ERROR] Failed to authenticate provider: Amazon Bedrock: DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:17:17.626654692+02:00 [ERROR] Failed to authenticate provider: Anthropic: DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:17:17.626765804+02:00 [ERROR] Failed to authenticate provider: DeepSeek: DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:17:17.626873139+02:00 [ERROR] Failed to authenticate provider: Google AI: DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:17:17.626985001+02:00 [ERROR] Failed to authenticate provider: Mistral: DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:17:18.264658441+02:00 [ERROR] Failed to authenticate provider: OpenAI: DBus error zbus error I/O error: No such file or directory (os error 2)
2025-04-09T18:23:17.217903392+02:00 [ERROR] window not found
So far nothing I've tried seems to work
Also, please share your hardware info as well, and please check if your drivers are up to date. Zed requires a
Vulkan compatible GPU,Vulkan 1.3 driver, and the following desktop portals:org.freedesktop.portal.FileChooser org.freedesktop.portal.OpenURI org.freedesktop.portal.Secret, or org.freedesktop.Secrets glibc version >= 2.35 is recommended.To make sure you have vulkan driver installed, can you please try vulkaninfo on your terminal?
Also please try
vkcube --gpu_number 0andvkcube --gpu_number 1In case everything is configured properly, both the commands should open up a window with a rotating cube on the display.
late reply, but i upgraded my drivers and packages locally and got it to work
Does this issue encompass the issue where the window becomes invisible after switching virtual desktop? (on X11, nvidia GPU). I haven't found any issue that fits better. Using XFCE (haven't tried other DEs), it always happen when switching. To make the window appear again, simply move the mouse cursor into where the window is (but invisible). Don't know enough (or anything, really) about how X11 does things but it feels like a redraw is missing (or maybe even happens too soon).
mte90 Desktop vkcube --gpu_number 1
Selected WSI platform: xcb
Selected GPU 1: Intel(R) HD Graphics 630 (KBL GT2), type: IntegratedGpu
vkcube: ./cube/cube.c:1486: demo_prepare_buffers: Assertion `!err' failed.
Annullato (core dump creato)
mte90 Desktop vkcube --gpu_number 2
Selected WSI platform: xcb
Selected GPU 2: llvmpipe (LLVM 19.1.7, 256 bits), type: Cpu
^C
mte90 Desktop vkcube --gpu_number 0
Selected WSI platform: xcb
Selected GPU 0: NVIDIA GeForce RTX 3060, type: DiscreteGpu
mte90 Desktop /home/mte90/.local/zed.app/libexec/zed-editor --system-specs
Zed System Specs (from CLI):
Zed: v0.194.3 (Zed)
OS: Linux Wayland debian 13
Memory: 15.5 GiB
Architecture: x86_64
GPU: <details><summary>`vulkaninfo --summary` output</summary>
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.309
Instance Extensions: count = 25
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_headless_surface : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 4
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
VK_NV_display_stereo : extension revision 1
Instance Layers: count = 8
--------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.280 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
Devices:
========
GPU0:
apiVersion = 1.3.280
driverVersion = 560.35.5.0
vendorID = 0x10de
deviceID = 0x2504
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA GeForce RTX 3060
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 560.35.05
conformanceVersion = 1.3.8.2
deviceUUID = a5687a0b-906d-65f7-6159-2d6b585e70ce
driverUUID = 606a4e01-6b53-50e2-972b-12653ee13a36
GPU1:
apiVersion = 1.4.311
driverVersion = 25.1.5
vendorID = 0x8086
deviceID = 0x5912
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 630 (KBL GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.1.5-0siduction1
conformanceVersion = 1.4.0.0
deviceUUID = 86801259-0400-0000-0002-000000000000
driverUUID = 6de8c30f-f45f-91ec-1a24-eea0fa6917e8
GPU2:
apiVersion = 1.4.311
driverVersion = 25.1.5
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 19.1.7, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 25.1.5-0siduction1 (LLVM 19.1.7)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3235-2e31-2e35-2d3073696400
driverUUID = 6c6c766d-7069-7065-5555-494400000000
</details>
On my tests.
If I run DRI_PRIME=1 WAYLAND_DISPLAY='' zed I get:
2025-07-14T16:42:02+02:00 INFO [zed] ========== starting zed ==========
2025-07-14T16:42:02+02:00 WARN [fontdb] Failed to load a font face 0 from '/usr/share/fonts/truetype/google-fonts/Khand-Black.ttf' cause font doesn't have a family name.
2025-07-14T16:42:02+02:00 WARN [fontdb] Failed to load a font face 0 from '/usr/share/fonts/truetype/google-fonts/Khand-ExtraBold.ttf' cause font doesn't have a family name.
2025-07-14T16:42:02+02:00 WARN [fontdb] Failed to load a font face 0 from '/usr/share/fonts/truetype/google-fonts/Khand-ExtraLight.ttf' cause font doesn't have a family name.
2025-07-14T16:42:02+02:00 WARN [fontdb] Failed to load a font face 0 from '/usr/share/fonts/truetype/google-fonts/Khand-SemiLight.ttf' cause font doesn't have a family name.
2025-07-14T16:42:02+02:00 INFO [gpui::platform::linux::x11::client] x11: compositor present: true, gtk_frame_extents_supported: true
2025-07-14T16:42:02+02:00 INFO [xim::x11rb] Try connect ibus
2025-07-14T16:42:02+02:00 INFO [db] Opening database /home/mte90/.local/share/zed/db/0-global/db.sqlite
2025-07-14T16:42:02+02:00 INFO [db] Opening database /home/mte90/.local/share/zed/db/0-stable/db.sqlite
2025-07-14T16:42:02+02:00 INFO [zed] Using git binary path: None
2025-07-14T16:42:02+02:00 INFO [prompt_store::prompts] No prompt template overrides directory found at /home/mte90/.local/share/zed/prompt_overrides. Using built-in prompts.
2025-07-14T16:42:02+02:00 INFO [assistant_tools::terminal_tool] agent selected bash for terminal tool
2025-07-14T16:42:02+02:00 INFO [gpui::platform::linux::platform] activate is not implemented on Linux, ignoring the call
2025-07-14T16:42:02+02:00 INFO [db] Opening database /home/mte90/.local/share/zed/db/0-stable/db.sqlite
2025-07-14T16:42:02+02:00 INFO [gpui::platform::linux::x11::window] Using Visual { id: 118, colormap: 0, depth: 32 }
2025-07-14T16:42:02+02:00 INFO [gpui::platform::linux::x11::window] Creating colormap 60817411
2025-07-14T16:42:02+02:00 ERROR [zed::reliability] {
"thread": "main",
"payload": "called `Result::unwrap()` on an `Err` value: ERROR_INITIALIZATION_FAILED",
"location_data": {
"file": "/home/ubuntu/.cargo/git/checkouts/blade-26bd638d88226de3/e0ec4e7/blade-graphics/src/vulkan/surface.rs",
"line": 340
},
"backtrace": [
"zed::reliability::init_panic_hook::{{closure}}::hf3a1cd12fb866d95+158039766",
"std::panicking::rust_panic_with_hook::h409da73ddef13937+131776323",
"std::panicking::begin_panic_handler::{{closure}}::h159b61b27f96a9c2+131775546",
"std::sys::backtrace::__rust_end_short_backtrace::h5b56844d75e766fc+131759705",
"__rustc[4794b31dd7191200]::rust_begin_unwind+131774685",
"core::panicking::panic_fmt::hc8737e8cca20a7c8+9606352",
"core::result::unwrap_failed::h727108008d9f4c9b+9607414",
"blade_graphics::hal::surface::<impl blade_graphics::hal::Context>::reconfigure_surface::h0e2c9e4521712a76+32824333",
"gpui::platform::blade::blade_renderer::BladeRenderer::new::h87946c10a720cf89+75594515",
"<gpui::platform::linux::x11::client::X11Client as gpui::platform::linux::platform::LinuxClient>::open_window::h32f1f3494b0873f0+75446327",
"gpui::platform::linux::platform::<impl gpui::platform::Platform for P>::open_window::h37c2e33aebce1d31+75123194",
"gpui::window::Window::new::hf9b39ddaa9bc34c6+75758016",
"gpui::app::async_context::AsyncApp::open_window::h59cf25260aa3dea5+150815025",
"workspace::Workspace::new_local::{{closure}}::{{closure}}::h69bc69032bf06218+152393120",
"gpui::app::App::spawn::{{closure}}::h4d30343735fd0c29+150922694",
"async_task::raw::RawTask<F,T,S,M>::run::h4f5dfaed8b47f176+150065501",
"<gpui::platform::linux::x11::client::X11Client as gpui::platform::linux::platform::LinuxClient>::run::h34fc388c66ff3219+75462162",
"gpui::platform::linux::platform::<impl gpui::platform::Platform for P>::run::h32665be0b6dd908f+75113853",
"gpui::app::Application::run::h8ffb63a755702f12+155578261",
"zed::main::h3dad0048345e6c52+158117910",
"std::sys::backtrace::__rust_begin_short_backtrace::hc3387f08456b172f+160038867",
"std::rt::lang_start::{{closure}}::h1997b1f261c830dd+160038841",
"std::rt::lang_start_internal::ha8ef919ae4984948+131689313",
"main+160038940",
"__libc_start_call_main+45312637639848",
"__libc_start_main_impl+45312637640037",
"_start+12569966"
],
"app_version": "0.194.3",
"app_commit_sha": "5df1775990dee09114a1423317561c34699f67ac",
"release_channel": "stable",
"target": "x86_64-unknown-linux-gnu",
"os_name": "Linux X11",
"os_version": "debian 13",
"architecture": "x86_64",
"panicked_on": 1752504122739,
"system_id": "48c789a8-5b2b-46ec-9ad5-e78078d71115",
"installation_id": "aefb58be-936d-4127-9914-9e979bdef51d",
"session_id": "8bf2b27f-fe00-4130-b863-d7a962679fb6"
}
I am on Debian with wayland and proprietary nvidia drivers. Seems nothing that can show up the window.
mte90 Desktop RUST_BACKTRACE=full zed --foreground
2025-07-18T10:21:28+02:00 INFO [zed] ========== starting zed ==========
thread 'main' panicked at crates/gpui/src/platform/linux/wayland/client.rs:500:47:
Unable to init GPU context: Platform(Init(ERROR_INITIALIZATION_FAILED))
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: __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
13: __libc_start_main_impl
at ./csu/../csu/libc-start.c:360:3
14: _start
stack backtrace:
0: 0x55bd1f047443 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h46a716bba2450163
1: 0x55bd19959443 - core::fmt::write::h275e5980d7008551
2: 0x55bd1f041c13 - std::io::Write::write_fmt::h561a66a0340b6995
3: 0x55bd1f0472a2 - std::sys::backtrace::BacktraceLock::print::hafb9d5969adc39a0
4: 0x55bd1f04b1da - std::panicking::default_hook::{{closure}}::hae2e97a5c4b2b777
5: 0x55bd1f04ad7a - std::panicking::default_hook::h3db1b505cfc4eb79
6: 0x55bd1f04b922 - std::panicking::rust_panic_with_hook::h409da73ddef13937
7: 0x55bd1f04b6ea - std::panicking::begin_panic_handler::{{closure}}::h159b61b27f96a9c2
8: 0x55bd1f047909 - std::sys::backtrace::__rust_end_short_backtrace::h5b56844d75e766fc
9: 0x55bd1f04b38d - __rustc[4794b31dd7191200]::rust_begin_unwind
10: 0x55bd1793aad0 - core::panicking::panic_fmt::hc8737e8cca20a7c8
11: 0x55bd1793aef6 - core::result::unwrap_failed::h727108008d9f4c9b
12: 0x55bd1b986002 - gpui::platform::linux::wayland::client::WaylandClient::new::hf37490e254d582ff
13: 0x55bd1b9e5885 - gpui::platform::current_platform::h120f6907a011e9d9
14: 0x55bd1b8f2b52 - gpui::app::Application::new::h76eeccbebb873c05
15: 0x55bd20b52649 - zed::main::h1474e7df545dae96
16: 0x55bd20b5df83 - std::sys::backtrace::__rust_begin_short_backtrace::h980277ba23f8ccb9
17: 0x55bd20b5df69 - std::rt::lang_start::{{closure}}::heaa7215c22909403
18: 0x55bd1f0365d1 - std::rt::lang_start_internal::ha8ef919ae4984948
19: 0x55bd20b5dfcc - main
20: 0x7f6d3e13cca8 - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
21: 0x7f6d3e13cd65 - __libc_start_main_impl
at ./csu/../csu/libc-start.c:360:3
22: 0x55bd17c1326e - _start
23: 0x0 - <unknown>
On Debian 12, I was able to get Zed working by updating Mesa from the backports repository:
sudo apt update
sudo apt install -t bookworm-backports mesa-vulkan-drivers mesa-va-drivers
If you get an error like E: The value 'bookworm-backports' is invalid for APT::Default-Release as such a release is not available in the sources, you need to add bookworm-backports to your sources and try again:
echo "deb http://deb.debian.org/debian bookworm-backports main" | sudo tee -a /etc/apt/sources.list
To start Zed, run:
export ZED_ALLOW_EMULATED_GPU=1
WAYLAND_DISPLAY="" zed
