On 09/25/2013 10:02 PM, Armin K. wrote: > On 09/25/2013 09:13 PM, Jan Alexander Steffens wrote: >> On Wed, Sep 25, 2013 at 6:08 PM, kristof <saposcat@xxxxxxxxxxx> wrote: >>> I'm not entirely savvy with all the details but from my understanding, >>> GNOME 3.10 will be featuring a Wayland tech preview, meaning that it can >>> (optionally?) use the wayland protocol to manage graphics and windows >>> and all that fun stuff. >>> >>> Are we going to compile this support by default? Does anyone know how >>> and if we'll be able to switch back and forth between Xorg and Wayland? >> >> It's all just ad-hoc in 3.10. For example, GDM has no support for Wayland. >> >> What you're supposed to do is log in on a VT (in text mode) and then >> run "gnome-session --session=gnome-wayland" to start the GNOME Shell. >> Alternatively, run "gnome-shell --wayland" from X to get a nested >> shell. >> >> However, at least for me it doesn't work at the moment: The shell >> launched from text mode just aborts with a trap, and the nested shell >> errors with: >> (gnome-shell-wayland:12690): Clutter-CRITICAL **: Unable to initialize >> Clutter: Failed to connected to any renderer due to constraints >> >> I'm a bit puzzled about how to fix this. I have Intel Sandy Bridge >> graphics, and the needed features of cogl and clutter are enabled. >> Insight welcome. >> >> I've already tried adding XWayland (xorg-server from xwayland branch >> with --enable-wayland, as well as xf86-video-wayland), but that didn't >> change anything. It's likely XWayland is needed anyway, but it seems >> my current problem is another one. >> > > You can use "mutter-launch -- gnome-shell-wayland --wayland" from a VT. > The clutter error seems to be there because cogl wasn't built with x11 > egl platform, but you shouldn't be getting that anyways. It's a bit ugly > when starting it this way (ie, nearly impossible to shut it down - > keybindings don't work, no vt switch), but it seems to start. > > Also, xwayland is required for gnome-shell-wayland to fire up. > Update, gnome-session --session=gnome-wayland works only as root when started from VT (for me). For some reason, xwayland dies when ran as normal user and gnome-shell-wayland traps.
