Bug 5582

Summary: Start Weston with systemd
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Ross Burton <ross.burton>
Component: graphicsAssignee: Alexander Kanavin <alex.kanavin>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: bluelightning, costin.c.constantin, holger.behrens, jku, kergoth, meta.mr.watcher, meta.watcher, sgw
Version: 1.5   
Target Milestone: 2.1   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Ross Burton 2013-11-21 15:42:22 UTC
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.
Comment 1 valentin 2014-04-02 11:21:16 UTC
Moved to 1.7
Comment 2 valentin 2014-07-15 13:04:05 UTC
patches sent on OE-core
Comment 3 Costin 2014-07-17 09:58:01 UTC
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
Comment 4 Ross Burton 2015-03-24 11:59:21 UTC
The patch set had problems and needs rebasing, resetting as appropriate.
Comment 5 Ross Burton 2015-04-28 18:48:31 UTC
Let's ignore user sessions for now and stick with system units.
Comment 6 Alexander Kanavin 2015-11-30 14:14:11 UTC
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).
Comment 7 Alexander Kanavin 2015-12-18 13:18:40 UTC
Solved in fccb12818a8bacdb59101ce5142af4caa4b2640a.