From 2e84ca6b7068a938b2f165a7c804ffa71f28b391 Mon Sep 17 00:00:00 2001 From: Ercan Date: Wed, 16 Sep 2026 11:49:53 +0200 Subject: [PATCH] fix: start:wayland defaults to wrong compositor socket WAYLAND_DISPLAY fell back to wayland-1 when unset, but that's not the real socket on every setup (wayland-0 on mine). With a saved pm2 env that never set WAYLAND_DISPLAY, electron connected to the wrong socket and SIGSEGV'd on every launch, and pm2's auto-restart turned that into a crash loop. Now it checks XDG_RUNTIME_DIR for the actual wayland-* socket first and only falls back to wayland-0 if it can't find one. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 735e19320c..e3d635350a 100755 --- a/package.json +++ b/package.json @@ -57,7 +57,7 @@ "server:watch": "node ./serveronly/watcher.js", "start": "node --run start:wayland", "start:dev": "node --run start:wayland -- dev", - "start:wayland": "WAYLAND_DISPLAY=\"${WAYLAND_DISPLAY:=wayland-1}\" ./node_modules/.bin/electron js/electron.js --ozone-platform=wayland", + "start:wayland": "WAYLAND_DISPLAY=\"${WAYLAND_DISPLAY:-$(ls \"${XDG_RUNTIME_DIR:-/run/user/$(id -u)}\" 2>/dev/null | grep -m1 '^wayland-[0-9]*$')}\"; WAYLAND_DISPLAY=\"${WAYLAND_DISPLAY:-wayland-0}\" ./node_modules/.bin/electron js/electron.js --ozone-platform=wayland", "start:wayland:dev": "node --run start:wayland -- dev", "start:windows": ".\\node_modules\\.bin\\electron js\\electron.js", "start:windows:dev": "node --run start:windows -- dev",