Zed only starts if ran with sudo on my arch linux.

[vinifrancosilva]

The same happens for installation via script, flatpak and pacman.

Here the logs:
2025-03-08T20:31:59.197370849-03:00 [INFO] ========== starting zed ==========
2025-03-08T20:31:59.462615917-03:00 [INFO] Presentation support: "VK_KHR_wayland_surface"
2025-03-08T20:31:59.46265852-03:00 [INFO] Presentation support: "VK_KHR_xcb_surface"
2025-03-08T20:31:59.462682657-03:00 [INFO] Presentation support: "VK_KHR_xlib_surface"
2025-03-08T20:31:59.462707325-03:00 [INFO] Enabling Vulkan Portability
2025-03-08T20:31:59.462728688-03:00 [INFO] Enabling color space support
2025-03-08T20:31:59.471849835-03:00 [INFO] Adapter: "NVIDIA GeForce GTX 1650"
2025-03-08T20:31:59.471942706-03:00 [INFO] No ray tracing extensions are supported
2025-03-08T20:31:59.565749266-03:00 [INFO] perform;
2025-03-08T20:31:59.565790585-03:00 [INFO] authenticate;
2025-03-08T20:31:59.565838402-03:00 [INFO] read_command;
2025-03-08T20:31:59.565896057-03:00 [INFO] send_secondary_commands;
2025-03-08T20:31:59.566013268-03:00 [INFO] Opening main db
2025-03-08T20:31:59.566299673-03:00 [INFO] new;
2025-03-08T20:31:59.566359439-03:00 [INFO] socket reader;
2025-03-08T20:31:59.566388201-03:00 [INFO] read_socket;
2025-03-08T20:31:59.566424167-03:00 [INFO] read_socket;
2025-03-08T20:31:59.566600239-03:00 [INFO] read_socket;
2025-03-08T20:31:59.566700103-03:00 [INFO] read_socket;
2025-03-08T20:31:59.566790236-03:00 [INFO] read_socket;
2025-03-08T20:31:59.567057455-03:00 [INFO] Opening main db
2025-03-08T20:31:59.567089303-03:00 [INFO] read_socket;
2025-03-08T20:31:59.567139389-03:00 [INFO] keep_updated;
2025-03-08T20:31:59.568562417-03:00 [INFO] Using git binary path: None
2025-03-08T20:31:59.568640028-03:00 [INFO] read_socket;
2025-03-08T20:31:59.569102915-03:00 [INFO] read_socket;
2025-03-08T20:31:59.569527026-03:00 [INFO] read_socket;
2025-03-08T20:31:59.56961309-03:00 [INFO] read_socket;
2025-03-08T20:31:59.569725744-03:00 [INFO] read_socket;
2025-03-08T20:31:59.569833077-03:00 [INFO] read_socket;
2025-03-08T20:31:59.569929009-03:00 [INFO] read_socket;
2025-03-08T20:31:59.570029752-03:00 [INFO] read_socket;
2025-03-08T20:31:59.570098015-03:00 [INFO] read_socket;
2025-03-08T20:31:59.579877327-03:00 [ERROR] Failed to load user settings: expected , or } at line 49 column 3
2025-03-08T20:31:59.593377304-03:00 [INFO] No prompt template overrides directory found at /home/vini/.local/share/zed/prompt_overrides. Using built-in prompts.
2025-03-08T20:31:59.595487561-03:00 [INFO] activate is not implemented on Linux, ignoring the call
2025-03-08T20:31:59.597516012-03:00 [INFO] perform;
2025-03-08T20:31:59.597563499-03:00 [INFO] authenticate;
2025-03-08T20:31:59.597605083-03:00 [INFO] read_command;
2025-03-08T20:31:59.597648138-03:00 [INFO] send_secondary_commands;
2025-03-08T20:31:59.597975632-03:00 [INFO] socket reader;
2025-03-08T20:31:59.598021263-03:00 [INFO] read_socket;
2025-03-08T20:31:59.598070719-03:00 [INFO] read_socket;
2025-03-08T20:31:59.600347609-03:00 [INFO] read_socket;
2025-03-08T20:31:59.601652009-03:00 [INFO] set environment variables from shell:/usr/bin/nu, path:/home/vini/.local/share/pnpm:/home/vini/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/home/vini/.local/share/flatpak/exports/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/vini/.duckdb/cli/latest:/home/vini/go/bin:/home/vini/.duckdb/cli/latest:/home/vini/go/bin
2025-03-08T20:31:59.601813902-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602082533-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602268282-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602298808-03:00 [INFO] new;
2025-03-08T20:31:59.602413217-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602493108-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602576786-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602819593-03:00 [INFO] read_socket;
2025-03-08T20:31:59.602889579-03:00 [INFO] keep_updated;
2025-03-08T20:31:59.603134517-03:00 [INFO] Opening main db
2025-03-08T20:31:59.6032038-03:00 [INFO] read_socket;
2025-03-08T20:31:59.603306593-03:00 [INFO] read_socket;
2025-03-08T20:31:59.603394441-03:00 [INFO] read_socket;
2025-03-08T20:31:59.606783504-03:00 [INFO] set status on client 0: Authenticating
2025-03-08T20:31:59.606955881-03:00 [INFO] perform;
2025-03-08T20:31:59.606995004-03:00 [INFO] authenticate;
2025-03-08T20:31:59.607048997-03:00 [INFO] read_command;
2025-03-08T20:31:59.607088092-03:00 [INFO] send_secondary_commands;
2025-03-08T20:31:59.607326067-03:00 [INFO] socket reader;
2025-03-08T20:31:59.607366267-03:00 [INFO] read_socket;
2025-03-08T20:31:59.607418086-03:00 [INFO] read_socket;
2025-03-08T20:31:59.608070559-03:00 [WARN] Rejected for not presenting to the window surface
2025-03-08T20:31:59.609500741-03:00 [ERROR] {
"thread": "main",
"payload": "called Result::unwrap() on an Err value: PlatformNotSupported",
"location_data": {
"file": "crates/gpui/src/platform/blade/blade_renderer.rs",
"line": 344
},
"backtrace": [
"__libc_start_main+24335649789260"
],
"app_version": "0.176.3",
"release_channel": "stable",
"target": "x86_64-unknown-linux-gnu",
"os_name": "Linux Wayland",
"os_version": "arch unknown",
"architecture": "x86_64",
"panicked_on": 1741476719609,
"system_id": "f80c076f-1102-4fd9-8960-b013e6c8dee3",
"installation_id": "2a17db24-fbbc-4405-b05a-2dfaf8783a9c",
"session_id": "2ea42963-9f68-4291-9b73-6c26f051e719"
}

PlatformNotSupported does not make sense since it runs when I use sudo.

Any ideas?

[Tonguechaude]

I have maybe an idea.

Zed likely needs access to your GPU device (e.g., /dev/dri/*)

When you run as sudo, you bypass normal user permissions — hence, it works.

As a regular user, if you're missing access to /dev/dri/renderD128 (or similar), GPU initialization will fail → PlatformNotSupported.

You can check permissions like:

ls -l /dev/dri/

Check if your user is in the video or render group:

groups $USER

If not, add yourself:

sudo usermod -aG video $USER
sudo usermod -aG render $USER

Then log out and log back in (or reboot).

---

You can also try to forcing X11 backend

Zed might not like your Wayland session. You can try launching it with:

env -u WAYLAND_DISPLAY zed

or even:

env GDK_BACKEND=x11 zed

Tell me if its works,

[vinifrancosilva]

Problem solved!

I was already a member of video group... checked the permissions with ls -l /dev/dri and it seems ok, so... this was not the solution:

drwxr-xr-x  2 root root       120 May 20 09:53 by-path
crw-rw----+ 1 root video 226,   0 May 20 09:53 card0
crw-rw----+ 1 root video 226,   1 May 20 09:53 card1
crw-rw-rw-  1 root video 226, 128 May 20 09:53 renderD128
crw-rw-rw-  1 root video 226, 129 May 20 09:53 renderD129

What did the trick for me was:

env -u WAYLAND_DISPLAY zed

Thank you very much for pointing this out!

Now I'm gonna create aliases and change the kde shortcut to include the command above!

If you need/want to test other solutions and options, count me in!

Thanks again!

[Tonguechaude]

@vinifrancosilva I answered your question ?

[vinifrancosilva]

OMG! Sorry for the late response! Did not see that there was responses here.

[Tonguechaude]

@vinifrancosilva No problem lmao