On 17.12.2014 20:05, Kaskinen, Tanu wrote:
Could VTNr=0 be a problem? On my Fedora laptop my graphical session
doesn't have TTY set, but VTNr is set to 1.
Well, if it is VTNr=2 it doesn't work either. VTNR is equal to
corresponding tty. Why is /dev/tty1 special here?
VTNR=1 == /dev/tty1
VTNR=2 == /dev/tty2
http://www.tldp.org/HOWTO/Text-Terminal-HOWTO-7.html#ss7.5
For example weston-launch requires that there's VT open, that's why we
open first free/unused VT (/dev/tty7) for genivi user, otherwise Weston
cannot start. This is the same that happens if you run "startx" from
normal Linux text login, it'll find first free VT and attach there. But
for user sessions that run on top of the system compositor, technically
there's no need to have any VT because they share the parent (genivi)
VT. And genivi session is not a normal user session and thus logind
doesn't know anything about it, otherwise it would attempt to launch all
systemd user services for it, such as crosswalk which is precisely what
we don't want. Similar to ssh sessions in current setup.
Or then someone would need to teach systemd/logind about different user
session types, that for session type X service set A is started and for
session type Z service B is started. Instead of blindly triggering
systemd --user and launching all user services for all logins regardless
of session type...
It should behave like we would be running under X, but it cannot detect
X because we use wayland instead.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
