mutter VS sway

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.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).