Go to file
Marek Chalupa 49ea6486e2 wayland: bind wayland socket after xwayland is initialized
During xwayland initialization we run main loop and dispatch wayland
events, so that xwayland can initialize. If some client during this
phase connects and creates surface, mutter crashes because
it is not initialized yet. If we bind wayland socket after xwayland
is initialized and main loop is not running anymore, no client can
connect to mutter during initialization and that is what we want.

https://bugzilla.gnome.org/show_bug.cgi?id=751845
2015-12-15 15:49:13 +01:00
data data: drop mutter-wayland.desktop 2015-11-09 10:25:40 -05:00
doc Remove gtk-doc 2015-07-06 00:52:18 -07:00
po Updated POTFILES.skip 2015-11-10 01:18:27 +01:00
src wayland: bind wayland socket after xwayland is initialized 2015-12-15 15:49:13 +01:00
tools Clean up the source tree 2014-03-18 20:37:35 -04:00
.gitignore Update .gitignore 2015-12-14 15:17:40 -08:00
autogen.sh build: Drop deprecated autogen.sh variables 2015-03-04 21:00:48 +01:00
configure.ac backends: Force 2-finger scroll by default if available 2015-12-15 14:38:23 +01:00
COPYING Updated obsolete FSF postal address in COPYING 2014-01-13 11:35:48 -05:00
Makefile.am Remove gtk-doc 2015-07-06 00:52:18 -07:00
mutter.doap doap: add <programming-language> 2014-07-31 17:50:28 +02:00
NEWS Bump version to 3.19.2 2015-11-25 00:34:28 +01:00