On systemd images we should investigate starting weston using a native unit instead of a rather evil init script. The recommended launcher is weston-launch but this may mean a hard requirement on PAM.
Moved to 1.7
patches sent on OE-core
Hello, Just tested the core-image-weston on genericx86-64: 1. Applied the patches from oe-core (related to this feature) 2. reverted Revert "cogl: update to 1.18.0", Revert "clutter: update to 1.18.2", Revert "cogl-1.0: update to 1.18.2", due to: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6514 After live boot on NUC, i could see Weston starting on tty1 and start the terminal using the shortcut in the left upper corner. Also I could also log in as root on tty2 and tty3. Regards, Costin
The patch set had problems and needs rebasing, resetting as appropriate.
Let's ignore user sessions for now and stick with system units.
Upstream has a task to add a reference unit file to the sources, but nothing has actually happened: https://phabricator.freedesktop.org/T63 At least they attached a couple of example unit files, and say that weston-launch should NOT be used (for reasons I'm not currently trying to understand).
Solved in fccb12818a8bacdb59101ce5142af4caa4b2640a.