-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zed failed to start on KDE Plasma 6 Wayland #17129
Comments
Same broken pipe os error 32 on Fedora 40 (Gnome and wayland) after updating stable zed to 0.150.4 from the app. When I launch it for the second time the protocol error message is different for me though: Zed.log``` 2024-08-30T13:18:54.257291303+02:00 [INFO] ========== starting zed ========== 2024-08-30T13:18:54.276897701+02:00 [INFO] Opening main db 2024-08-30T13:18:54.276958064+02:00 [INFO] perform; 2024-08-30T13:18:54.277034241+02:00 [INFO] authenticate; 2024-08-30T13:18:54.277122649+02:00 [INFO] read_command; 2024-08-30T13:18:54.278880332+02:00 [INFO] new; 2024-08-30T13:18:54.278958841+02:00 [INFO] socket reader; 2024-08-30T13:18:54.279055862+02:00 [INFO] Using git binary path: None 2024-08-30T13:18:54.279657218+02:00 [INFO] keep_updated; 2024-08-30T13:18:54.305723711+02:00 [INFO] initializing context server client 2024-08-30T13:18:54.305849702+02:00 [INFO] Registering built-in prompt template: content_prompt 2024-08-30T13:18:54.306074813+02:00 [INFO] Registering built-in prompt template: edit_workflow 2024-08-30T13:18:54.306147897+02:00 [ERROR] No such file or directory (os error 2) about ["/home/yaymalaga/.config/github-copilot"] 2024-08-30T13:18:54.306296456+02:00 [INFO] Registering built-in prompt template: step_resolution 2024-08-30T13:18:54.306642257+02:00 [INFO] Registering built-in prompt template: terminal_assistant_prompt 2024-08-30T13:18:54.30702561+02:00 [INFO] No prompt template overrides directory found at /home/yaymalaga/.local/share/zed/prompt_overrides. Using built-in prompts. 2024-08-30T13:18:54.307433792+02:00 [INFO] extensions updated. loading 4, reloading 0, unloading 0 2024-08-30T13:18:54.309230744+02:00 [INFO] performance metrics display disabled 2024-08-30T13:18:54.309286649+02:00 [INFO] activate is not implemented on Linux, ignoring the call 2024-08-30T13:18:54.310632994+02:00 [INFO] Opening main db 2024-08-30T13:18:54.311214169+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.311289233+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.311341934+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.311395443+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.311503495+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.31158205+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.311640935+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.312068738+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.312128036+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.312172801+02:00 [INFO] perform; 2024-08-30T13:18:54.312232012+02:00 [INFO] authenticate; 2024-08-30T13:18:54.312296654+02:00 [INFO] read_command; 2024-08-30T13:18:54.312572539+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:54.313432263+02:00 [INFO] socket reader; 2024-08-30T13:18:54.320313251+02:00 [INFO] new; 2024-08-30T13:18:54.321429338+02:00 [INFO] keep_updated; 2024-08-30T13:18:54.36023533+02:00 [INFO] set environment variables from shell:/bin/bash, path:/home/yaymalaga/.local/bin:/home/yaymalaga/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/yaymalaga/Android/flutter/bin:/home/yaymalaga/Android/Sdk/platform-tools:/home/yaymalaga/Android/Sdk/emulator:/home/yaymalaga/.pub-cache/bin:/home/yaymalaga/Android/flutter/bin:/home/yaymalaga/Android/Sdk/platform-tools:/home/yaymalaga/Android/Sdk/emulator:/home/yaymalaga/.pub-cache/bin 2024-08-30T13:18:56.058251094+02:00 [INFO] Enabling Vulkan Portability 2024-08-30T13:18:56.058316469+02:00 [INFO] Enabling color space support 2024-08-30T13:18:56.085856474+02:00 [INFO] Adapter "Intel(R) Graphics (RPL-S)" 2024-08-30T13:18:56.085903086+02:00 [INFO] No ray tracing extensions are supported 2024-08-30T13:18:56.08928964+02:00 [INFO] Using surface present mode MAILBOX 2024-08-30T13:18:56.089490067+02:00 [WARN] Unable to forbid exclusive full screen 2024-08-30T13:18:56.089754505+02:00 [INFO] Creating a descriptor pool for at most 16 sets 2024-08-30T13:18:56.089803866+02:00 [INFO] Creating a descriptor pool for at most 16 sets 2024-08-30T13:18:56.089850757+02:00 [INFO] Initializing Blade pipelines for surface SurfaceInfo { format: Bgra8UnormSrgb, alpha: PreMultiplied } 2024-08-30T13:18:56.094813737+02:00 [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 24.1.6" } 2024-08-30T13:18:56.095228784+02:00 [INFO] set status on client 0: Authenticating 2024-08-30T13:18:56.09585538+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:56.095940378+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:56.096957114+02:00 [INFO] perform; 2024-08-30T13:18:56.097020807+02:00 [INFO] authenticate; 2024-08-30T13:18:56.09708218+02:00 [INFO] read_command; 2024-08-30T13:18:56.097838088+02:00 [INFO] socket reader; 2024-08-30T13:18:56.098883804+02:00 [INFO] Opening main db 2024-08-30T13:18:56.104778355+02:00 [INFO] new; 2024-08-30T13:18:56.10625509+02:00 [INFO] keep_updated; 2024-08-30T13:18:56.147571657+02:00 [WARN] unhandled message: Metadata(SupermavenMetadataMessage { dust_strings: None }) 2024-08-30T13:18:56.147622809+02:00 [WARN] unhandled message: Set(SupermavenSetMessage { key: "disabled", value: Bool(false) }) 2024-08-30T13:18:56.147809235+02:00 [INFO] Opening main db 2024-08-30T13:18:56.149072344+02:00 [INFO] Initializing default prettier with plugins {} 2024-08-30T13:18:56.149311091+02:00 [INFO] set status on client 198664: Connecting 2024-08-30T13:18:56.150073967+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:56.150203012+02:00 [ERROR] no worktrees when constructing ProjectLspAdapterDelegate 2024-08-30T13:18:56.175120071+02:00 [INFO] Initializing default prettier with plugins {} 2024-08-30T13:18:56.175672938+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:56.197734168+02:00 [INFO] Initializing default prettier with plugins {} 2024-08-30T13:18:56.198252884+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:18:56.616682199+02:00 [INFO] Initializing default prettier with plugins {} 2024-08-30T13:18:56.617316401+02:00 [WARN] request completed with error: failed to connect to the server 2024-08-30T13:19:01.520975869+02:00 [INFO] connected to rpc endpoint https://collab.zed.dev/rpc 2024-08-30T13:19:02.078730471+02:00 [INFO] add connection to peer 2024-08-30T13:19:02.07878102+02:00 [INFO] add_connection; 2024-08-30T13:19:02.078824162+02:00 [INFO] waiting for server hello 2024-08-30T13:19:02.07901525+02:00 [INFO] got server hello 2024-08-30T13:19:02.079046405+02:00 [INFO] set status to connected (connection id: ConnectionId { owner_id: 0, id: 0 }, peer id: PeerId { owner_id: 504, id: 797550 }) 2024-08-30T13:19:02.079099364+02:00 [INFO] set status on client 198664: Connected { peer_id: PeerId { owner_id: 504, id: 797550 }, connection_id: ConnectionId { owner_id: 0, id: 0 } } ``` |
The same issue for me, I am on Fedora 40 KDE Spin (Wayland), but for me the editor launches normally if opened it as sudo: The output of
And the output of
I attached the Zed.log (zed was run normally not as sudo): Zed.log
For the Zed.log of the root user after running |
I encounter also a failure at startup on Fedora 40, but the error message is slightly different with zed latest stable and preview:
Are you all using a nvidia card with the latest driver? |
Yes I am on a laptop that has intel integrated graphics (Intel UHD Graphics 620) and NVIDIA GeForce 940MX with nvidia drivers v560.35.03 Here are my machine's specs: ➜ inxi -b
System:
Host: fedora Kernel: 6.10.6-200.fc40.x86_64 arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.1.4 Distro: Fedora Linux 40 (KDE Plasma)
Machine:
Type: Laptop System: HP product: HP Pavilion Laptop 15-cc1xx
v: Type1ProductConfigId serial: <superuser required>
Mobo: HP model: 83F9 v: 46.53 serial: <superuser required> UEFI: Insyde
v: F.36 date: 08/16/2021
Battery:
ID-1: BAT0 charge: 43.4 Wh (100.0%) condition: 43.4/43.4 Wh (100.0%)
CPU:
Info: quad core Intel Core i7-8550U [MT MCP] speed (MHz): avg: 1175
min/max: 400/4000
Graphics:
Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
Device-2: NVIDIA GM108M [GeForce 940MX] driver: nvidia v: 560.35.03
Device-3: Quanta HP Wide Vision HD Camera driver: uvcvideo type: USB
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris
gpu: i915,nvidia resolution: 1920x1080
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.6
renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
Drives:
Local Storage: total: 1.35 TiB used: 259.24 GiB (18.8%)
Info:
Memory: total: 16 GiB available: 15.5 GiB used: 5.98 GiB (38.6%)
Processes: 360 Uptime: 2h 58m Shell: Zsh inxi: 3.3.34 |
This is a bug with the Nvidia 560 drivers. Going back to the 555 drivers or running Zed with Xwayland, or using a compositor that doesn't support explicit sync, resolves the issue for me. |
The issue is also tracked at nividia? |
if you don't want to downgrade your Nvidia driver, you can run zed as below
Ref. #16863 |
I've reported it in the 560 release feedback thread but it doesn't seem to have been given any notice... am just using Zed in Xwayland for the time being. |
If you give the link to the report, people hitting the issue will be able to add weight to it. |
https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/360 here's the link. It doesn't mention Zed directly but rather wgpu, but it's the same issue in their driver. |
After updating to the the latest Nvidia open-source kernel module 560, zed doesn't open but consumes lot of CPU cycles in the background. One of my cores were at 96 deg C! Fedora 40, Gnome 46 This is the error -
|
This is the exact same issue I have, no errors. I’m on Nobara 40 (a tweaked flavor of Fedora 40), Gnome 46, Nvidia 560 drivers and Wayland |
I think it's best to report it to Nvidia by acknowledging the bug posted by @edwloef on the NVIDIA forums - https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/360 |
flatpak user can try: |
sadly, can't fix the issue for me. Here is my log:
Using a hybrid (Intel iGPU + NVIDIA dGPU) laptop |
I had a similar issue with the igpu not being able to display, the problem was that the prime-mode was set to nvidia changing it to on-demand solved it for me.
vkcube now works with --gpu_number 0,1,2 |
It's probably not a KDE issue, as I can reproduce it in Hyprland. |
Happens on GNOME for me |
ditching NVIDIA drivers and using Nouveau+NVK is a only possible solution until NVIDIA fixes their drivers |
Happening on KDE Plasma 6 with AMDGPU drivers. |
I have found another solution that worked for me. Reading Arch documentation on the NVIDIA drivers there are two kernel settings mentioned. With current 560 drivers provided with Arch and these two kernel parameters zed is launching perfectly fine. I won't claim to fully understand the ramifications of these settings, but they do mention being required for Wayland compositors to work properly. Reference: https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting nvidia_drm.modeset=1 |
Confirming the bug happens for me as well on: KDE Plasma 6 (Wayland) Hardware: Intel IGPU & AMD GPU Workaround works:
|
Seems like same issue |
same issue, after disabling dGPU using |
I encounter same problem after I updated Nvidia drivers on my Fedora Linux. Downgrade to Zed 0.155.2
OS: Fedora Linux 40 (Workstation Edition) x86_64
Kernel: Linux 6.10.12-200.fc40.x86_64
Display (NCP0056): 1920x1080 @ 60 Hz in 14″ [Built-in]
DE: GNOME 46.5
WM: Mutter (Wayland)
WM Theme: Adwaita
CPU: 11th Gen Intel(R) Core(TM) i5-11320H (8) @ 4.50 GHz
GPU 1: NVIDIA GeForce MX450 [Discrete]
GPU 2: Intel Iris Xe Graphics @ 1.35 GHz [Integrated]
UPD: I also experienced problems with other software in Wayland session. Driver downgrade help me with that also. So probably it's not Zed issue, but something between Nvidia drivers and Wayland. |
Hey, Not sure this is related: I get a slightly different error (using the flatpack version on KDE Neon, Zed 0.157.5 ):
and the Does anyone have an Idea if this is the same or a different Issue? Best, Andreas |
I detected that removing the package vulkan-intel on Arch Linux magically resolved my issue. |
Same Error here, since I installed Ubuntu 24.10 Ubuntu 24.10 with Linux 6.11.0-9-generic Running with DRI_PRIME=1 works |
This has been unsolved for several months. Is there any work being done to fix it? I'm gonna have to switch back to vscode if this is just gonna be a permanent issue. |
On my machine, this has the same effect as running with |
Its working without flags on hyprland |
I went deeper into the code and this problem is not related to OS, DE, or ZED. It's a Wayland issue. The updates on explicit sync broke some of the functions I assume. If you look at the logs below,
and with
It indicates that it can't create a surface. This might be solved within the blade library with some error handling but I doubt it's the right way to do it. We should expect driver (egl-wayland?) maintainers to fix this issue. In the meantime, the best solution is using
or if you want to run it on Nvidia GPU (there are some glitches)
Let's not ping Zed maintainers on this issue anymore, they can't help. |
works. That makes sense - this started happening once KDE got explicit sync support |
Seems to be fixed on Fedora 41 with latest NVIDIA driver. |
Can confirm it is working now. This issue can be closed. |
It works now without the |
Seems to be OK on Arch here - nvidia 565.57.01 |
That's the update I just got in rpm fusion on Fedora, previous version was 560. |
To summarize for people arriving later: You are likely looking at this issue if Zed is failing to launch and you have a setup with ALL 3 of these:
And you are seeing messages like this in Zed's error logs in the terminal:
There are a few ways to deal with the issue:
Given that it goes away when upgrading the NVIDIA driver to 565.x.y which specifically advertises Wayland support improvements and there are mentions of other software having similar issues in such setups I'm inclined to believe this was a bug in NVIDIA's Wayland support and as such I'll close this issue for now. (There definitely are still issues with Zed's Wayland code e.g. resizing being slow/stuttery but I think those are better handled as their own issues.) |
Check for existing issues
Describe the bug / provide steps to reproduce it
extra/zed 0.150.4-1
andzed-git 0.151.0.r67.g02cd512-1
)When I launch zed from a fresh boot, it outputs:
then exit.
When I launch it second time, it outputs a huge log until i kill it:
Environment
My system info:
Wayland info: https://paste.mozilla.org/ZBEqvK87
If applicable, attach your
~/Library/Logs/Zed/Zed.log
file to this issue.Zed.log
The text was updated successfully, but these errors were encountered: