gnome-vrr VS sway

https://copr.fedorainfracloud.org/coprs/kylegospo/gnome-vrr/ :

  gsettings set org.gnome.mutter experimental-features "['variable-refresh-rate']"

This probably isn't what you're looking for, but by enabling this: https://copr.fedorainfracloud.org/coprs/kylegospo/gnome-vrr/ you can get vrr/vsync on Wayland for gnome, it can cause flickering but otherwise it's pretty good and got rid of any tearing and stuttering for me.

You can grab the patch from https://github.com/KyleGospo/gnome-vrr and build it.

Source: https://github.com/KyleGospo/gnome-vrr/issues/5

Based on the comments in the AUR repo, I'd assume that the maintainer still invests time trying to update mutter-vrr. There seems to be a non-trivial issue when rebasing on Gnome 44, but I'm not able to assess how complex the problem actually is. (https://github.com/KyleGospo/gnome-vrr/issues/5)

Currently you can either use a Wayland DE that supports VRR, I know KDE has support for it, or use the gnome-vrr copr or build it yourself from his GitHub.

For fedora you can use https://copr.fedorainfracloud.org/coprs/kylegospo/gnome-vrr/

Just wanted to share my updated PKGBUILD to enable VRR in Gnome 43.2. The original author has no time to update his AUR package it seems so i updated it myself with the sources from the Fedora COPR.

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).