4 Commits

Author	SHA1	Message	Date
Jasper St. Pierre	8cb9cfb7b8	Revert "meta-weston-launch: Call VT_ACTIVATE ourselves" ... This reverts commit ebe6e3180e. This is wrong, as mutter's controlling TTY may not be the same as the active VT, and in fact won't be in the case of systemd spawning us. The "correct" API for this is to use David Herrmann's "Session Positions" system to switch to another VT: http://lists.freedesktop.org/archives/systemd-devel/2013-December/014956.html	2014-01-16 13:42:07 -05:00
Jasper St. Pierre	1d3dbea20c	meta-weston-launch: Don't use a GObject here ... We don't need a complicated API anymore.	2013-12-31 19:22:16 -05:00
Jasper St. Pierre	ebe6e3180e	meta-weston-launch: Call VT_ACTIVATE ourselves ... We don't need any special permissions, so we don't need to go through weston-launch to do so...	2013-12-31 19:22:16 -05:00
Giovanni Campagna	e72f81c24f	wayland: add TTY and DRM master management ... Now that we have a setuid launcher binary, we can make use of using a private protocol through the socket we're passed at startup. We also use the new hook in clutter-evdev to ask mutter-launch for the FDs of the input devices we need, and we emulate the old X DRM lock with a nested GMainContext without sources. In the future, mutter-launch will be replaced with the new logind API currently in development. https://bugzilla.gnome.org/show_bug.cgi?id=705861	2013-08-30 10:32:55 +02:00