]> code.ossystems Code Review - meta-freescale.git/commit
weston-init: Fix inoperable Weston desktop
authorTom Hochstein <tom.hochstein@nxp.com>
Tue, 26 Jun 2018 02:11:45 +0000 (21:11 -0500)
committerOtavio Salvador <otavio@ossystems.com.br>
Thu, 5 Jul 2018 18:32:27 +0000 (15:32 -0300)
commit6c50f608063f673f8763d2baebf1c486cb5ed63a
tree5c452a28b6a849e6397c46a8e426a6c90cf6bd16
parent3650dc2b1d17ea3d3c0388a890592f89c47d84de
weston-init: Fix inoperable Weston desktop

For an image configured with pam and systemd, Weston apps
would fail to run. For example:

$ weston-terminal
failed to connect to Wayland display: No such file or directory
failed to create display: No such file or directory

This fix is based on a proposal by Daniel Diaz to OE-core. The
main part of the fix is the use of a new, manually created tty.

The original proposal called weston directly, but that didn't
seem to work where weston-launch did.

Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
recipes-graphics/wayland/weston-init.bbappend
recipes-graphics/wayland/weston-init/imxdrm/weston.config [new file with mode: 0644]
recipes-graphics/wayland/weston-init/mx8mm/weston.config [new file with mode: 0644]
recipes-graphics/wayland/weston-init/weston.config [new file with mode: 0644]
recipes-graphics/wayland/weston-init/weston.service [new file with mode: 0644]