linux/poky.git/meta/recipes-graphics/wayland/weston-init/weston@.service, branch master

weston-init: Stop running weston as root

2020-11-24T10:27:45+00:00

Running the weston compositor as the root user is an insecure default behavior for OE-core. We can do much better, at least when using systemd. Change the recipe to create a dedicated "weston" user and start weston as this user. The systemd service and socket units are no longer template units, as there were several inconsistencies in the templates. Instead, there is now a global /run/wayland-0 socket that gets created, and systemd will start weston on demand when a client connects to that socket or when attempting to reach graphical.target, whichever comes first. This also allows downstream users to easily change the behavior so that weston *only* starts on demand by adding a drop file. Access to the global socket is controlled by a "wayland" group; any user that is a member of the group can use the socket to talk to the compositor. This also satisfies another use case where another systemd service might start a graphical application that needs to display with weston (e.g. a single function device in kiosk mode). Finally, the udev rules for starting weston with the existance of a DRM device have been removed. Being WantedBy= a graphical target should eliminate the need for this behavior, and having it present makes it difficult for downstream users to start weston on demand (having to override the udev rules). (From OE-Core rev: dd83fb40f76749c6689807afabc63b9d5c2a4065) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

weston-init: Add environment file support for systemd unit file

2020-10-06T22:14:25+00:00

The /etc/default/weston file is already installed and it can be used as systemd EnvironmentFile. (From OE-Core rev: a1390bd294a0f21297ace3f7b4e33912fa9cb63b) Signed-off-by: Fabio Berton Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

weston-init: Redefine weston service and add socket activation option

2020-09-10T12:48:27+00:00

Currently, weston when autolauched with systemd ends up with seat0 related errors because its launched before seat0 is assigned. Fixes [05:16:09.357] logind: failed to get session seat [05:16:09.358] logind: cannot setup systemd-logind helper (-61), using legacy fallback The above error results in ptest failures in parselogs, even though weston has started ok using fallback methods, these errors are still seen in logs Also fixes weston ptests RESULTS - weston.WestonTest.test_weston_can_initialize_new_wayland_compositor: PASSED (8.58s) (From OE-Core rev: c21fa5a291ab207a084285935ab73a0b4225c965) Signed-off-by: Khem Raj Cc: Marek Vasut Cc: Henning Heinold Signed-off-by: Richard Purdie

weston-init: Let weston run without pam on distros without pam

2020-01-11T15:19:27+00:00

When pam is not part of distro, user specific XDG_* environment variables are not available since PAMName=login is in-effective and as a result weston can not start because it direly needs XDG_RUNTIME_DIR defined, therefore launching weston directly in systemd service will not work, therefore call the helper script weston-start, which is also used with sysvinit extend enabling fbdev backend fallback to all qemu machines Reported-by: Marek Vasut (From OE-Core rev: ae66cf5e03f04361aad2bd8784fb7d42e0f0bb08) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

weston-init: Add possibility to run weston as non-root user

2019-09-19T14:27:02+00:00

These changes are from meta-96boards primarily Launch the session via a udev rule based on what kind of display device is available delete weston-conf and move the fuctionality into weston-init other layers are doing same weston-init installs machine specific weston.ini therefore mark is machine specific now (From OE-Core rev: aa3bced2e1de2f4ba507aa014835b06edccc138a) Signed-off-by: Khem Raj Cc: Otavio Salvador Signed-off-by: Ross Burton Signed-off-by: Richard Purdie