On Sat, Jan 04, 2014 at 06:44:36PM +0800, Yin Kangkai wrote: > On 2014-01-03, 21:13 -0800, Kok, Auke-jan H wrote: > > Patrick and me have been working on a solution upstream, both with > > parts in systemd and in user-session-units. We can now start a logind > > session properly for either wayland or Xorg. > > OK, may I know when will that land in Tizen?
The first iteration of this code has already been submitted for Tizen 3.0 in the user-session-units package. I know it was accepted in the IVI project, and I'm pretty sure the SR was accepted for Mobile as well. If the Mobile package is up-to-date, there is a new systemd service available to use for starting a logind session at bootup. It is named '[email protected]'. The instance name requires a specific format, SEAT-UID, so you can quickly give it a test run by running: systemctl enable [email protected] and reboot. In the IVI 3.0 kickstart file, the symlink is created manually in the /usr/lib/systemd hierarchy, so the Mobile kickstart file should do the same. > > the environment stuff is something that should be done -inside- of the > > user session - meaning it should be done by a unit that is run by the > > systemd --user daemon. Also note that hardcoding DISPLAY=:0 is > > absolutely not what we want upstream, since that would mean that you > > could never have a display on :1, etc.... This needs more work, a lot > > more work. > > Agree with not hard coding of the DISPLAY=:0 > Other than that, what's the difference of setting ENV inside user > session with a unit, and setting it in [email protected] with > "Environment="? When set in [email protected], all child processes of 'systemd --user' inherit the variable(s), but have a service defining variables might not have the same effect. To avoid defining DISPLAY in [email protected], you could define it in a service.d conf file instead, but it still means hardcoding the ":0". Some example contents: $ cat /usr/lib/systemd/system/[email protected]/env.conf [Service] Environment=DISPLAY=:0 > Anyway, this is too early to talk into this level of details, you're > right, this still needs a lot of work seems. We will try to contribute > here as well. Yes, there are still a few major issues to sort out, especially to make user sessions more future proof and align more with upstream. Regards, Patrick _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
