Variable rate refresh (VRR / FreeSync / Adaptive-Sync) support for GNOME’s Mutter compositor is closer to being merged. The native back-end support for VRR that has been in development the past two years is no longer considered a work-in-progress and it’s believed there are no longer any blocking issues that would prevent this code from landing.
Every modern compositor should support this.
Note that one of the things holding it back is that a standard protocol for communicating VRR support status under Wayland hasn’t been settled on yet and Mutter’s current MR just blindly assumes all clients (i.e. applications) won’t break or glitch if the user toggles VRR on.
Kwin Wayland do support VRR already, and if the milestone tag at their issue tracker is to be believed, merged and shipped since Plasma 5.22.
https://invent.kde.org/plasma/kwin/-/merge_requests/718
But I never had the chance to test it, I don’t have the right hardware (my monitor do support freesync, but it so old that their refresh range is just too small to make a difference).
I don’t know if that ever broke any application.
The fact that Wayland necessitates every compositor to implement this is pure unmitigated insanity: https://gitlab.freedesktop.org/wayland/wayland/-/issues/233
And it shows. Wayland is Gnome/Mutter, or GTFO.
Yeah, from your bug report
“This all sounds like too high of a price to pay for ostensibly improved security guaranteed by Wayland. Not a single person however has provided a single proof of X.org’s “insecurity” ever having been abused to gain unauthorized access to the user account. To abuse X.org’s insecurity model you first need to be able to run applications within the user session and at least Linux users normally don’t run random applications from the net.”
Sorry but this is just wrong. Driveby attacks are still a thing. Library malware payloads have been in the wild for like a decade, and that’s just one way of injecting code into a benign application. And there is nothing making Linux more resistant to driveby compromise than Windows or OSX – in fact, modern versions of those OSes have security features like control flow integrity that most Linux distros don’t. Most of the Linux desktop’s security at this point is just obscurity.
FFS, show me successful attacks against Xorg PLEASE, OK?
And tell me how many people have been hacked by those attacks, OK?
Also, since Xorg is so f*cking insecure what if I give you my IP address or visit any of your websites and you’ll try to hack me?
It’s amazing what Wayland does to people, it replaces grey matter with actual crap.
.
.
.
TLDR: STOP talking crap about things you know and understand nothing about. Xorg’s “insecurity” is NOT what you think it is. Lastly it’s not been fixed, it’s right there a GAPING hole I presume. Too bad it’s not used.
.
.
.
Also this f*cking bug report/feature request is NOT about Xorg FFS! It’s about Wayland being a crap incomplete protocol which makes each compositor implement a CRAPTON of features which only RedHat/KDE can do. All other minor DEs and WMs? Eat crap, said Wayland developers.
.
XFCE? No plans to support Wayland.
JWM/IceWM/etc. – Wayland support rejected!
LXQT? Nothing definitive.
.
.
Is Linux about choice? Well, woohoo, Wayland makes sure you either run Gnome or KDE or nothing.