[Linux] Zed does not lunch with latest update #17776
Comments
bknightInfo
added
admin read
Moshyfawn
added
linux
linux-x11
|
Same problem on Zed version: 0.152.3, Zed version: 0.151.2 logsZed version: 0.152.3 logs |
|
Same here, no internal/external GPU, NixOS, Wayland. With XWayland it works: Wayland logSystem informationOS: NixOS 24.11.20240913.345c263 (Vicuna) x86_64 |
In your case I see a NVIDIA GPU. You might have success with what worked for me when using the NVIDIA 560 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 |
Thanks, but it didn't help, this is what's happening
I found a solution for Zed version: >= 0.152.3 - #17129 (comment) but it's only works with integrated gpu. |
This indeed works. On NixOS, you just need to run Zed Ver: 0.152.4 |
This comment was marked as outdated.
This comment was marked as outdated.
|
Of course not, zed still does not work with integrated graphics. Forcing discrete graphics is a very inefficient and weird solution, especially for people who do not have them. |
|
Could you paste your graphics card driver details/versions? |
|
I have both amdvlk and radv. |
|
I know it's a PITA but would you be willing to test zed with only the open source driver (uninstall the proprietary driver, restart, then launch zed) and then again with only the proprietary driver (uninstall the open source, restart and relaunch zed) and see if either of those configurations works better than your current config with both drivers? I seen multiple folks reporting the various environment variables for selecting drivers not behaving quite as expected (e.g. only disabling the proprietary shader compiler not the entire proprietary driver), but once they just had a single driver things behaved better. |
|
My work arounds no longer work anymore so I will switch back unfortunately to vs code still its resolved thread 'main' panicked at crates/gpui/src/platform/linux/x11/client.rs:253:75: |
|
FWIW, this seems to be partly a Hyprland issue. I use Sway as well as Labwc (both Wayland compositors) and have had no troubles with Zed. To get Hyprland to start, I used the workaround mentioned above. System informationOS: Arch Linux 2024-10-03 |
This just makes it start in a XWayland session instead, not in native Wayland. So the problem is we can't launch zed on Wayland-native on integrated GPUs.
On another note, I can seem to start zed in native Wayland just fine after updating my system today (with the latest |
|
I'm sorry, but the problem seems to have gone away for me now due to a user error on my part. I found out I had some unpurged junk from the flatpak version of Zed, and by removing that and rebooting the system So sorry for the confusion. |
|
I get the same problem on WSL, ubuntu 22 if i try to run with and i get unsupported GPU |
Check for existing issues
Describe the bug / provide steps to reproduce it
With the latest update Zed doesn't seem to working on Linux as it just won't run.
I am thinking its probably a bug with Wayland since no one else seems to be reporting it.
No real steps it just wont run
error: "payload": "called
Result::unwrap()on anErrvalue: ERROR_INITIALIZATION_FAILED",Environment
Zed Ver: 0.152.3
OS: Arch Linux Wayland
Memory: 32 GiB
Architecture: x86_64
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 6700 XT
If applicable, attach your
~/Library/Logs/Zed/Zed.logfile to this issue.Zed.log
The text was updated successfully, but these errors were encountered: