[Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

blackout23 · 2015-03-25 16:09:18

Hi,

first of all thanks for packaging the new release so quickly. I haven't found any major bugs this far.

With Gnome 3.16 on Wayland GTK & Co. should favor the Wayland backend instead of starting on XWayland, when available. This seems to work fine for pure GTK apps like gedit & Co.
When I launch the Control Center under Wayland it doesn't start up. When I start it in a terminal it tells me "Clutter-Gtk-Error *** Unsupported Backend".
So I have to use "CLUTTER_BACKEND=wayland gnome-control-center" to start it up.

I tried out a Fedora 22 nightly on a USB stick and there the control center starts without having to specify the Wayland backend for clutter.

Regards

Last edited by blackout23 (2015-04-09 10:46:04)

pogeymanz · 2015-03-25 18:02:16

I am also affected by this bug.

Also, how can we check for sure that GDM is using Wayland? As I understand, it should fall back to X silently if Wayland fails.

blackout23 · 2015-03-25 18:09:17

pogeymanz wrote:

I am also affected by this bug.
Also, how can we check for sure that GDM is using Wayland? As I understand, it should fall back to X silently if Wayland fails.

It does run on Wayland by default with open source drivers. Unless you uncomment out EnableWayland=false in /etc/gdm/custom.conf. You can run htop and you will see something like, /usr/bin/gdm --displayserver --wayland etc. Or /usr/bin/mutter --gdm --displayserver --wayland.

Last edited by blackout23 (2015-03-25 18:10:22)

pogeymanz · 2015-03-25 18:29:29

Thanks blackout. Do you have at least 24 forum and/or social media accounts?

I just wasn't sure if seeing /usr/bin/gdm --displayserver --wayland was definitive proof or not. I guess if it failed, it would have relaunched without the wayland flag.

blackout23 · 2015-03-25 19:03:41

pogeymanz wrote:

Thanks blackout. Do you have at least 24 forum and/or social media accounts?
I just wasn't sure if seeing /usr/bin/gdm --displayserver --wayland was definitive proof or not. I guess if it failed, it would have relaunched without the wayland flag.

I have more. With different nicknames even.

It does launch on X after failing to start Wayland. A bit of an ugly drawback is, that it basically means it segfaults once when you use it with proprietary drivers. You will see a coredump in "coredumpctl". So people who use proprietary drivers should just change /etc/gdm/custom.conf or Arch Linux could make it use X11 by default again, with the modified custom.conf.

Jodell · 2015-03-27 22:15:33

Totem seems to be affected as well. It still crashes on startup though.

ooo · 2015-04-07 08:55:38

clutter 1.22 should be using gdk backend by default instead of x11 or wayland.

I'm not sure if it's built in the arch package though, clutter build script checks for gdk3 and builds the gdk backend if it's present on build system. However the clutter PKGBUILD doesn't depend on gtk3, so I'm guessing the gdk backend is left out.

heftig · 2015-04-09 07:34:19

ooo wrote:

clutter 1.22 should be using gdk backend by default instead of x11 or wayland.
I'm not sure if it's built in the arch package though, clutter build script checks for gdk3 and builds the gdk backend if it's present on build system. However the clutter PKGBUILD doesn't depend on gtk3, so I'm guessing the gdk backend is left out.

~~That was reverted upstream before the release of 1.22.0.~~

Actually, I can't find the commit about this anymore. Maybe I'm wrong, but I remember *something* was switched from GDK back to X11 backend...

Last edited by heftig (2015-04-09 08:16:27)

heftig · 2015-04-09 08:16:36

Anyway, I rebuilt clutter with the GDK backend. GNOME on Wayland is less painful now.

ooo · 2015-04-09 09:08:57

heftig wrote:

~~That was reverted upstream before the release of 1.22.0.~~
Actually, I can't find the commit about this anymore. Maybe I'm wrong, but I remember *something* was switched from GDK back to X11 backend...

Looks like they reverted to x11 at one point, but switched back to gdk after fixing some regressions.
It's even mentioned in release notes that gdk backend is the new default.

heftig wrote:

Anyway, I rebuilt clutter with the GDK backend. GNOME on Wayland is less painful now.

nice!

blackout23 · 2015-04-09 10:58:34

Yes this works now. Emmanuelle Bassi, a clutter developer, told me that Clutter and GTK3 should both use the GDK Backend. So this is the right behavior, now.
http://www.reddit.com/r/linux/comments/ … ?context=3

Arch Linux

#1 2015-03-25 16:09:18

[Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#2 2015-03-25 18:02:16

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#3 2015-03-25 18:09:17

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#4 2015-03-25 18:29:29

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#5 2015-03-25 19:03:41

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#6 2015-03-27 22:15:33

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#7 2015-04-07 08:55:38

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#8 2015-04-09 07:34:19

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#9 2015-04-09 08:16:36

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#10 2015-04-09 09:08:57

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

#11 2015-04-09 10:58:34

Re: [Fixed] Gnome 3.16 - Clutter doesn't favor the Wayland backend

Board footer