linux/poky.git/meta/recipes-graphics/wayland, branch master-test

libinput: upgrade 1.16.3 -> 1.16.4

2020-12-09T12:20:33+00:00

(From OE-Core rev: 4d3ebeef202d9c0544749b64d47e269d939a5124) Signed-off-by: Zang Ruochen Signed-off-by: Richard Purdie

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: Fix incorrect idle-time setting

2020-11-17T21:53:14+00:00

(From OE-Core rev: 84b3a6b7bd73ebad90865ee4351578c2109358fb) Signed-off-by: Alistair Francis Signed-off-by: Richard Purdie

libinput: upgrade 1.16.2 -> 1.16.3

2020-11-17T21:53:13+00:00

(From OE-Core rev: e710f7cf11d494c057f7065f9fc271b7e4e85d62) Signed-off-by: Zang Ruochen Signed-off-by: Richard Purdie

weston: add pam to REQUIRED_DISTRO_FEATURES

2020-11-16T14:27:46+00:00

* it was added to weston-init in 72dd74c5d384dbe641cc7c02ecf766ff8d5f555f now world builds are failing with: ERROR: Nothing RPROVIDES 'weston-init' (but openembedded-core/meta/recipes-graphics/wayland/weston_9.0.0.bb RDEPENDS on or otherwise requires it) weston-init was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) NOTE: Runtime target 'weston-init' is unbuildable, removing... Missing or unbuildable dependency chain was: ['weston-init'] ERROR: Nothing RPROVIDES 'weston-dev' (but openembedded-core/meta/recipes-graphics/wayland/weston_9.0.0.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'weston-dev' NOTE: Runtime target 'weston-dev' is unbuildable, removing... Missing or unbuildable dependency chain was: ['weston-dev'] ERROR: Nothing RPROVIDES 'weston' (but openembedded-core/meta/recipes-graphics/wayland/weston_9.0.0.bb RDEPENDS on or otherwise requires it) No eligible RPROVIDERs exist for 'weston' NOTE: Runtime target 'weston' is unbuildable, removing... Missing or unbuildable dependency chain was: ['weston'] (From OE-Core rev: 0a882490fe75915c7a119f3498df6750be25f8e0) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

wayland-utils: introduce a recipe

2020-11-11T10:08:12+00:00

wayland-utils contains wayland-info utility which deprecates and replaces weston-info from weston. (From OE-Core rev: bb8fa9950e716fdcee818a38dc4df3a19b1f3c2f) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

weston-init: fall back to fbdev under x32

2020-11-11T10:08:12+00:00

Otherwise, there's a crash in swrast - the same issue as with X11. (From OE-Core rev: 09ef3dacc55544143a146190c3d66fcf5dc697ad) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

weston-init: correctly start under systemd

2020-11-11T10:08:12+00:00

Several issues are addressed: 1. weston requires pam when starting under systemd 2. systemd was attempting to launch weston twice (from sysvinit script and from systemd unit file) which caused confusion and errors. 3. runtime test should stop/start weston via systemd only if systemd actually controls system startup, not merely when systemd is present. (From OE-Core rev: 72dd74c5d384dbe641cc7c02ecf766ff8d5f555f) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

weston: Fix linking with LTO

2020-11-11T10:08:11+00:00

weston uses --no-undefined option during linking which does not work with LTO therefore override it with -z undefs when lto is enabled in distro (From OE-Core rev: c5252fc88938ab3425595dcf31f892ed4aba6bc1) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

weston-init: introduce WESTON_GROUP

2020-11-08T14:03:20+00:00

Currently the WESTON_USER variable is used as user and group name for chown'ing XDG_RUNTIME_DIR. If WESTON_USER has no group with the same name this fails. Therefore add a new WESTON_GROUP variable which is set to WESTON_USER if not specified to ensure backwards compatibility. (From OE-Core rev: 8d4e0ac61671646749a30c72782376307b3e0c82) Signed-off-by: Richard Leitner Signed-off-by: Richard Purdie