gnome-unstable VS mutter

You can try with unstable gnome but since it is intended to use with Arch you may be cautious since it can lead to problems.

You can add to your mirrorlist the FCGU mirror and install unofficially the Gnome 43

I just installed Gnome 43 on arch using the FCGU repository and I'm very surprised on how snappy and fast the system feels. Normally the overview has some slowdowns and low fps, on fedora is even worse (I blame the energy profile thingy) but with 43 everything flies and runs very fast! I'll live on gnome for a few weeks at least, but I thing I'll keep this instalation for a while

Until then, you can try the unstable fcgu repo.

If you want it that bad you can just use the unstable repo

If you’re keen to try it you can use this: https://gitlab.com/fabiscafe/gnome-unstable

Bored? why wait?

That depends on the time of the year. I'm the maintainer of the GNOME-Unstable repo FGCU. So normally I spend no time at all to the repo… maybe a few minutes a week, except when GNOME does alpha, beta and early stable releases. Where this can end up with around 4, 5h some day.

what's the difference between this and the fcgu repo?

Kewl. I guess the bug report should go to https://gitlab.gnome.org/GNOME/mutter

Regarding Ubuntu Gnome Wayland, I heard that there is the possibility to get VRR working with mutter-vrr (and gnome-control-center-VRR ?) https://gitlab.gnome.org/GNOME/mutter

You should create an issue in https://gitlab.gnome.org/GNOME/mutter for this.

As a result I'm studying the wayland architecture (I like gnome so the compositor would be Mutter) so that I can figure out how to either make a hack or make something legitimate. This is proving time consuming.

Hmm.. I'm not sure about the negativo drivers, but if you need EGLstreams working it seems like there are a few build options for mutter you can use? https://github.com/GNOME/mutter/blob/main/meson_options.txt

pkgname=mutter pkgver=42.0 pkgrel=0.1 pkgdesc="A window manager for GNOME" url="https://gitlab.gnome.org/GNOME/mutter" arch=(x86_64) license=(GPL) depends=(dconf gobject-introspection-runtime gsettings-desktop-schemas libcanberra startup-notification zenity libsm gnome-desktop upower libxkbcommon-x11 gnome-settings-daemon libgudev libinput pipewire xorg-xwayland graphene libxkbfile libsysprof-capture) makedepends=(git gobject-introspection egl-wayland meson xorg-server wayland-protocols sysprof) checkdepends=(xorg-server-xvfb wireplumber python-dbusmock) provides=(libmutter-10.so) groups=(gnome) _commit=9249aba72a5c4454894c08735a4963ca1665e34d # tag/42.00 source=( "git+https://gitlab.gnome.org/GNOME/mutter.git#commit=$_commit" "https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441.patch" ) sha256sums=('SKIP' 'SKIP')

Mutter

Wayland is a protocol - not an implementation. It tries to minify latency by merging together some of the components X11 had and tries to do this in a slim and faster way.

The implementation of the protocol may differ, but I know for example MUTTER (https://gitlab.gnome.org/GNOME/mutter)

This article has nice and not too complex visualisations: https://www.secjuice.com/wayland-vs-xorg/

Stock Mutter - in contrast to this fork of it - would not work either.