Reproduction steps
Untill the last update, Zed always opened as expected, both via terminal with the command zeditor and by the menu.
After the last update it doesn't show up any window, the application exits immediately without leaving any message.
I've tried removing .local/share/zed/db as suggested here but for Mac but nothing changed.
Opening htop I've found something interesting: the process with the command /usr/lib/zed/zed-editor zed-cli:///tmp/.tmpiyBuU2/socket was still there in sleeping state, and a SIGTERM was enough to close it.
That said, after trying opening it again, I've read the log file shown in the dedicated section of this issue: the first lines suggest me that removing db and generating it again didn't solve the issue. The last line of the log file shows a json file:
[
{
"thread_name":"Worker-1","thread_id":15794382300316794652,"timings":[]
},
{
"thread_name":"Worker-0","thread_id":6185506036438099345,"timings":[{
"location":{
"file":"crates/extension_host/src/wasm_host.rs","line":659,"column":22
},"start":935398625,"duration":400970737
}
]
},
{
"thread_name":"Worker-2","thread_id":18147521187885925800,"timings":[]
},
{
"thread_name":"Worker-3","thread_id":7364705619221056123,"timings":[]
},
{
"thread_name":"main","thread_id":2206609067086327257,"timings":[]
},
{
"thread_name":"Timer","thread_id":2404222719611925354,"timings":[]
}
]I hope I've given you all the informations you need, in a separed section I've added the system specs.
Zed version and system specs
Version 1.26.2 installed by official repos OS: Arch Linux (kernel: 7.2.11-arch1-1 ) Graphic Server: Wayland Graphics Card: Intel Broadwell-U GT2 [HD Graphics 5500] GPU Driver: i915
Since Zed doesn't even open up, I can't use zed: copy system specs into clipboard
Attach Zed log file
Zed.log
2026-10-30T13:35:26+01:00 INFO [util] raised open file soft limit from 1024 to 65536
2026-10-30T13:35:26+01:00 INFO [zed] ========== starting zed version 1.26.2+stable, sha unknown ==========
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 11 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 12 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 12 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 13 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 14 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 15 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 16 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 17 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 18 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 19 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 20 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 26 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 26 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 27 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 27 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 27 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [sqlez::migrations] Found 28 foreign key relationships to check
2026-10-30T13:35:27+01:00 INFO [gpui_linux::linux::platform] Compositor GPU hint: vendor=0x8086, device=0x1616 (from dev 226:128)
2026-10-30T13:35:27+01:00 WARN [zed::reliability] Minidump endpoint not set
2026-10-30T13:35:27+01:00 INFO [zed::reliability] memory usage: resident 89 MiB, virtual 827 MiB
2026-10-30T13:35:27+01:00 INFO [extension_host] extensions updated. loading 4, reloading 0, unloading 0
2026-10-30T13:35:27+01:00 INFO [gpui_linux::linux::platform] activate is not implemented on Linux, ignoring the call
2026-10-30T13:35:27+01:00 INFO [zed::reliability] worktree diagnostics: projects 0, orphaned projects 0, stores 0, slots 0, live 0, visible 0, strong 0, dead weak 0, loading 0, entries 0, visible entries 0, largest none
2026-10-30T13:35:27+01:00 INFO [prompt_store::rules_to_skills_migration] Starting rules-to-skills migration; skills_dir=/home/user/.agents/skills, agents_md=/home/user/.config/zed/AGENTS.md, prompts_dir=/home/user/.local/share/zed/prompts
2026-10-30T13:35:27+01:00 INFO [prompt_store::rules_to_skills_migration] Rules-to-skills migration found 0 non-default rules and 0 default rules
2026-10-30T13:35:27+01:00 INFO [gpui_linux::linux::platform] activate is not implemented on Linux, ignoring the call
2026-10-30T13:35:27+01:00 INFO [prompt_store::rules_to_skills_migration] Finished rules-to-skills migration; skill_names=0, agents_md_names=0, customized_builtins=0
2026-10-30T13:35:27+01:00 ERROR [x_ai_subscribed] Failed to load SuperGrok credentials: DBus error service error org.freedesktop.zbus.Error: The name is not activatable
2026-10-30T13:35:27+01:00 ERROR [openai_subscribed] Failed to load ChatGPT subscription credentials: DBus error service error org.freedesktop.zbus.Error: The name is not activatable
2026-10-30T13:35:27+01:00 INFO [gpui_wgpu::wgpu_context] Found 1 GPU adapter(s):
2026-10-30T13:35:27+01:00 INFO [gpui_wgpu::wgpu_context] - Intel(R) HD Graphics 5500 (BDW GT2) (vendor=0x8086, device=0x1616, backend=Vulkan, type=IntegratedGpu)
2026-10-30T13:35:27+01:00 INFO [gpui_wgpu::wgpu_context] Testing adapter: Intel(R) HD Graphics 5500 (BDW GT2) (Vulkan)...
2026-10-30T13:35:27+01:00 INFO [gpui_wgpu::wgpu_context] Adapter Intel(R) HD Graphics 5500 (BDW GT2) (Vulkan) failed: no compatible surface formats, trying next...
2026-10-30T13:35:27+01:00 ERROR [crates/client/src/client.rs:391] DBus error service error org.freedesktop.zbus.Error: The name is not activatable
2026-10-30T13:35:27+01:00 INFO [util] set environment variables from shell:/bin/zsh, path:/home/user/.local/share/pnpm:/usr/condabin:/usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/lib/rustup/bin:/home/user/.local/bin:/home/user/.rush/bin:/home/user/.npm-global/bin:/home/user/.local/bin:/home/user/.local/bin:/home/user/.rush/bin:/home/user/.npm-global/bin
2026-10-30T13:35:28+01:00 INFO [zed::reliability::hang_detection::logging] New foreground hang detected:
Tasks(s) that ran too long
104.310545ms - crates/workspace/src/workspace.rs:2184:12
2026-10-30T13:35:28+01:00 INFO [zed::reliability::hang_detection::logging] Background hang detected on Worker-1:
Tasks(s) that ran too long
151.874247ms - crates/gpui/src/app.rs:3451:34
2026-10-30T13:35:28+01:00 INFO [zed::reliability::hang_detection::logging] Background hang detected on Worker-0:
Tasks(s) that ran too long
745.191544ms - crates/extension_host/src/wasm_host.rs:659:22
400.383304ms - crates/extension_host/src/wasm_host.rs:659:22
2026-10-30T13:35:28+01:00 INFO [zed::reliability::hang_detection::logging] Background hang detected on Worker-3:
Tasks(s) that ran too long
788.51857ms - crates/zed/src/main.rs:446:14
2026-10-30T13:35:28+01:00 INFO [zed::reliability::hang_detection] Task trace has been saved to: /home/user/.local/share/zed/hang_traces/hang-2026-10-30_13-35-28.miniprof.jsonActivity
7
- The output of
/usr/lib/zed/zed-editor --system-specs. Use the editor binary rather than thezeditorCLI launcher. If the output is missing Vulkan information, also sharevulkaninfo --summary, including any errors.
Sure. The printed result shows Vulkan informations too. Reading the format I guess it has to be read as Markdown, but since I'm not sure I'm just reporting the raw result as is.
2026-10-30T14:43:07+01:00 INFO [util] raised open file soft limit from 1024 to 65536
Zed System Specs (from CLI):
Zed: v1.26.2+stable (Zed)
OS: Linux Wayland arch
Memory: 7.5 GiB
Architecture: x86_64
GPU: <details><summary>`vulkaninfo --summary` output</summary>
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.363
Instance Extensions: count = 26
-------------------------------
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_layer_settings : extension revision 2
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
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_maintenance1 : extension revision 1
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
Instance Layers: count = 6
--------------------------
VK_LAYER_MESA_anti_lag Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 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.354
driverVersion = 26.2.6
vendorID = 0x8086
deviceID = 0x1616
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 5500 (BDW GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 26.2.6-arch1.1
conformanceVersion = 1.3.0.0
deviceUUID = 86801616-0900-0000-0002-000000000000
driverUUID = c5d8832d-f5f8-c9a3-0b81-ec48d8bdb1d0
</details>
- Fresh terminal output from
ZED_LOG=wgpu=info zeditor --foreground ., after terminating the leftover Zed process.
I'm not sure to undestand this point correctly, but I've terminated the process and executed the command; this appeared:
2026-10-30T14:58:10+01:00 INFO [util] raised open file soft limit from 1024 to 65536
2026-10-30T14:58:10+01:00 INFO [zed] ========== starting zed version 1.26.2+stable, sha unknown ==========
2026-10-30T14:58:10+01:00 INFO [gpui_linux::linux::platform] Compositor GPU hint: vendor=0x8086, device=0x1616 (from dev 226:128)
2026-10-30T14:58:10+01:00 WARN [zed::reliability] Minidump endpoint not set
2026-10-30T14:58:10+01:00 INFO [zed::reliability] memory usage: resident 104 MiB, virtual 827 MiB
2026-10-30T14:58:10+01:00 INFO [extension_host] extensions updated. loading 4, reloading 0, unloading 0
2026-10-30T14:58:10+01:00 INFO [prompt_store::rules_to_skills_migration] Rules-to-skills migration already marked done; skipping startup migration
2026-10-30T14:58:10+01:00 INFO [gpui_linux::linux::platform] activate is not implemented on Linux, ignoring the call
2026-10-30T14:58:10+01:00 INFO [zed::reliability] worktree diagnostics: projects 0, orphaned projects 0, stores 0, slots 0, live 0, visible 0, strong 0, dead weak 0, loading 0, entries 0, visible entries 0, largest none
2026-10-30T14:58:10+01:00 INFO [gpui_linux::linux::platform] activate is not implemented on Linux, ignoring the call
2026-10-30T14:58:10+01:00 ERROR [x_ai_subscribed] Failed to load SuperGrok credentials: DBus error service error org.freedesktop.zbus.Error: The name is not activatable
2026-10-30T14:58:10+01:00 ERROR [openai_subscribed] Failed to load ChatGPT subscription credentials: DBus error service error org.freedesktop.zbus.Error: The name is not activatable
2026-10-30T14:58:10+01:00 ERROR [crates/client/src/client.rs:391] DBus error service error org.freedesktop.zbus.Error: The name is not activatable
2026-10-30T14:58:10+01:00 INFO [project::trusted_worktrees] Worktree "/home/joey_bland/Sardegna" is not trusted
2026-10-30T14:58:10+01:00 INFO [gpui_wgpu::wgpu_context] Found 1 GPU adapter(s):
2026-10-30T14:58:10+01:00 INFO [gpui_wgpu::wgpu_context] - Intel(R) HD Graphics 5500 (BDW GT2) (vendor=0x8086, device=0x1616, backend=Vulkan, type=IntegratedGpu)
2026-10-30T14:58:10+01:00 INFO [gpui_wgpu::wgpu_context] Testing adapter: Intel(R) HD Graphics 5500 (BDW GT2) (Vulkan)...
2026-10-30T14:58:10+01:00 INFO [gpui_wgpu::wgpu_context] Adapter Intel(R) HD Graphics 5500 (BDW GT2) (Vulkan) failed: no compatible surface formats, trying next...
2026-10-30T14:58:10+01:00 ERROR [zed::zed::open_listener] failed to open workspace [/home/joey_bland/Sardegna]: No GPU adapter found that can configure the display surface
error opening [/home/joey_bland/Sardegna]: No GPU adapter found that can configure the display surface
2026-10-30T14:58:11+01:00 INFO [zed::reliability::hang_detection::logging] New foreground hang detected:
Tasks(s) that ran too long
106.130204ms - crates/workspace/src/workspace.rs:2184:12
2026-10-30T14:58:11+01:00 INFO [zed::reliability::hang_detection::logging] Background hang detected on Worker-0:
Tasks(s) that ran too long
155.824333ms - crates/gpui/src/app.rs:3451:34
2026-10-30T14:58:11+01:00 INFO [zed::reliability::hang_detection::logging] Background hang detected on Worker-1:
Tasks(s) that ran too long
510.704111ms - crates/extension_host/src/wasm_host.rs:659:22
296.558533ms - crates/extension_host/src/wasm_host.rs:659:22
255.081466ms - crates/extension_host/src/wasm_host.rs:659:22
2026-10-30T14:58:11+01:00 INFO [zed::reliability::hang_detection] Task trace has been saved to: /home/joey_bland/.local/share/zed/hang_traces/hang-2026-10-30_14-58-11.miniprof.json
2026-10-30T14:58:40+01:00 INFO [zed::reliability] memory usage: resident 304 MiB (+200 MiB), virtual 14654 MiB
2026-10-30T14:58:40+01:00 INFO [zed::reliability] worktree diagnostics: projects 0, orphaned projects 0, stores 0, slots 0, live 0, visible 0, strong 0, dead weak 0, loading 0, entries 0, visible entries 0, largest noneAfter that I've pressed ctlr + c.
- Your compositor name and version, Mesa and Vulkan driver package versions, and the last Zed version that worked.
The version of Mesa package, that contains the drivers, is 1:26.2.6-1, Vulkan drivers for Intel GPU has the same version 1:26.2.6-1.
I don't remember without any doubt what Zed version worked last time, but since I update frequently it may be the last one before the 1.26.2-1.
- Whether
vkcubeworks in Wayland mode, and whetherWAYLAND_DISPLAY="" zeditor --foreground .opens Zed through XWayland, if available. Terminate any leftover Zed process before each launch test.
Yes, executing this command opened the window correctly this time. And after closing the window the process no longer appears in sleep state.
I've also tried WAYLAND_DISPLAY="" zeditor and WAYLAND_DISPLAY="" zeditor --foreground, both worked.
Does that mean it was a Wayland problem? Thank you anyway for your time!
PS: I'm still not sure if it's the case to close the issue or to wait.
@JoeyBland013 Can you share your compositor name and version? Also, did you test vkcube in Wayland mode separately, or were those results only for Zed? I need that result to narrow down the native Wayland failure.
Oh sorry @yeskunall . Executing vkcube shows... a cube, what I may expect I guess, and it says that the WSI platform is wayland, I hope it's what you need. Talking about my compositor I don't know what you are referring to, can you be more precise?
@JoeyBland013 Yes, that’s the test I needed. Since vkcube works on Wayland, Vulkan can open a window there, but Zed still fails.
By compositor, I mean the software managing your windows, such as GNOME’s Mutter, KDE’s KWin, Sway, or Hyprland. If you’re unsure, can you run echo "$XDG_CURRENT_DESKTOP" and share the output? That should help me identify which one you’re using.
@yeskunall I'm using Hyprland, I've omitted that information because I thought it was not needed.
Hey there, I'm also on hyprland, wasn't able to reproduce. Might be more related to your graphical drivers.... instead of Zed specifically.
@JoeyBland013 can you try opening another GPUI application and see if it fails aswell?
@JoeyBland013 The log points to a graphics initialization failure:
Intel(R) HD Graphics 5500 … failed: no compatible surface formats. The database messages are informational, so there’s no need to delete the database again. You can collect diagnostics without opening a window. The Linux graphics-reporting docs cover this. Can you share the following so I can narrow down the cause?/usr/lib/zed/zed-editor --system-specs. Use the editor binary rather than thezeditorCLI launcher. If the output is missing Vulkan information, also sharevulkaninfo --summary, including any errors.ZED_LOG=wgpu=info zeditor --foreground ., after terminating the leftover Zed process.vkcubeworks in Wayland mode, and whetherWAYLAND_DISPLAY="" zeditor --foreground .opens Zed through XWayland, if available. Terminate any leftover Zed process before each launch test.