On systems without systemd, weston-launch requires the existence of the weston-launch group and approprate permissions on the weston-launch binary. Pasting details from the building Wayland page (http://wayland.freedesktop.org/building.html): ---- For KMS/DRM output (outside of X) use weston-launch, which needs root permissions, which are set if "make install" is run as root, but some distributions disable it. It also requires that you enable systemd session support for weston-launch (by using systemd and having the systemd-login devel headers at configure time) or add yourself to the "weston-launch" group: $ sudo groupadd weston-launch $ sudo usermod -a -G weston-launch $USER $ # Log all the way out (of X, etc.) $ sudo chown root weston-launch $ sudo chmod +s weston-launch $ weston-launch
Currently, weston-launch is installed with setuid bit by default. It was once done in the x11 overlay to replace weston-launch with the video group: http://git.overlays.gentoo.org/gitweb/?p=proj/x11.git;a=blob;f=dev-libs/weston/weston-9999.ebuild;h=520b6252b66375620524370b4b13ac8ef8413bf2;hb=60585ac753299de9fc296c234992073db53a7ebd#l94
This has been fixed in weston-9999 with the introduction of seatd btw and doesn't seems to require the weston-launch mess anymore.
I'm going to close this anyway as it has long worked via setuid. That's not ideal but it was the best we could do until seatd came along.
