[SOLVED] Wayland fails to execute

Message

roboto · Post by **roboto** » Sat Jan 06, 2018 1:27 am

I compiled x11-base/xorg-server with wayland USE flag and this enabled on all other installed packages. I have xwayland enabled. I installed dev-libs/sway and typed /usr/bin/sway.

Then, this happened. SwayWM did nothing but print this error message:

Code: Select all

[main.c:48] [wlc] Failed to add socket to wayland display

I tried to find a main.c, but to no avail. Any help is appreciated.
Thanks.

mike155 · Post by **mike155** » Sat Jan 06, 2018 1:52 am

1) You could turn on logging:

sway -dV >/tmp/sway-output 2>&1

2) If you emerged sway with use flag "tray", you'd better execute "export $(dbus-launch)" before starting sway.

roboto · Post by **roboto** » Sat Jan 06, 2018 3:36 am

The log gave me a bunch of unset variables. i.e. SWAY_CURSOR_THEME=(null)

Is there a guide out there telling me what to set these variables to?

The fatal error in the log shows:

Code: Select all

[main.c:52] [wlc] error: XDG_RUNTIME_DIR not set in the environment

Again, what value do I set these variables to?

Mr. T. · Post by **Mr. T.** » Sat Jan 06, 2018 12:58 pm

I have the impression that the Gentoo community does not have the resource to help the mass.

Gentoo does not set the variable XDG_RUNTIME_DIR.

Reference: https://wayland.freedesktop.org/building.html - look at the section "Running Weston".

mike155 · Post by **mike155** » Sat Jan 06, 2018 12:59 pm

If you don't know how to set XDG_RUNTIME_DIR, look here for a code snippet: https://wiki.gentoo.org/wiki/Weston

I recommend to get Weston up and running before installing any other Wayland compositor. Weston is small, it's easy to install and configure, and it's fun. If Weston works, you can be sure that Wayland and your low level graphics drivers work. Then you can move on to the Wayland compositor and the desktop environment you want to install. If you get any errors, you can be sure that they are related to your Wayland compositor or your desktop environment - and not to Wayland or low level graphics drivers.

Post by **asturm** » Sat Jan 06, 2018 1:02 pm

Wayland itself doesn't 'work'. It is *always* the compositor of your choice that may be better or worse. Now, of course you can check if your graphics stack is prepared for Wayland, but you can have that much cheaper: nvidia-drivers works not, everything else does.

mike155 · Post by **mike155** » Sat Jan 06, 2018 1:55 pm

Gentoo does not set the variable XDG_RUNTIME_DIR.

That depends on your system/service manager. As far as I know, pam_systemd sets this environment variable: https://www.freedesktop.org/software/sy ... stemd.html

roboto · Post by **roboto** » Sat Jan 06, 2018 4:31 pm

SwayWM works now due to the building weston guide telling me to set the variable to a temporary directory in /tmp and giving it 0700 permissions.

Thank you all for your time.

josephg · Post by **josephg** » Sun Jan 07, 2018 12:19 pm

mike155 wrote:If you don't know how to set XDG_RUNTIME_DIR, look here for a code snippet: https://wiki.gentoo.org/wiki/Weston

I recommend to get Weston up and running before installing any other Wayland compositor. Weston is small, it's easy to install and configure, and it's fun. If Weston works, you can be sure that Wayland and your low level graphics drivers work. Then you can move on to the Wayland compositor and the desktop environment you want to install. If you get any errors, you can be sure that they are related to your Wayland compositor or your desktop environment - and not to Wayland or low level graphics drivers.

thanks to this thread, i finally got some motivation to look at wayland. i installed weston, and it runs beautifully

then i installed sway.. had to fiddle a bit, and now it feels just like my i3. overall very functional, but not ready for primetime yet. i can compare any sway glitches with weston, and can see that almost all issues are sway only.