Can not run wayland applications under stardust

I built stardust-xr-server on Arch, started it with its own XDG_RUNTIME_DIR (otherwise my desktop becomes unusable), and tried to connect weston-terminal to it with WAYLAND_SOCKET=/tmp/stardust-xr-0/wayland-0 weston-terminal. Weston-terminal only outputs this:
failed to connect to Wayland display: Success
failed to create display: Success
failed to connect to Wayland display: Success
failed to create display: Success
Other wayland applications fail with the same or similar messages.
23 Replies
nvme0n1p1
nvme0n1p19mo ago
Happens on both main and develop branch
Nova
Nova9mo ago
wait what specifically do you mean your desktop becomes unusable if it's the same runtime dir that's def important to figure out
nvme0n1p1
nvme0n1p19mo ago
Because I can't start anything anymore because things try to use the wayland socket and fail
Nova
Nova9mo ago
ah you're using Xorg on your 2D desktop aren't you?
nvme0n1p1
nvme0n1p19mo ago
Yes
Nova
Nova9mo ago
that'll do it! but manually setting the socket should still work so try develop branch on server always
nvme0n1p1
nvme0n1p19mo ago
I did try develop branch
Nova
Nova9mo ago
just keep it on develop I mean
nvme0n1p1
nvme0n1p19mo ago
Ok
Nova
Nova9mo ago
are you running an nvidia GPU? just curious
nvme0n1p1
nvme0n1p19mo ago
Nope, AMD
Nova
Nova9mo ago
cool I don't think it matters but may as well check that error message is horribly vague @i509VCB any ideas? :S
i509VCB
i509VCB9mo ago
that message is from libwayland? Although that's incredibly odd
Nova
Nova9mo ago
I assume so yea
i509VCB
i509VCB9mo ago
wuh why would strerror be returning Success on failure? wl_display_connect doesn't say anything about errno being changed is weston-terminal getting a connection failure and reading the default errno value? (the message is not from libwayland)
Want results from more Discord servers?
Add your server