It has something to do with drawing, because over some surfaces it doesn't happen, but all gtk native apps exhibit it. This is a 7900x with an intel a750 graphics card. It should not happen.
Anyway, I realized I really don't like gnome. I used it for 13 months and installed all different extensions to deal with issues. Then I realized that this is just the mac os experience, and that I personally really don't like it. Now I am migrating to KDE, which takes 10 minutes to configure and can then be foegotten, and I wont get a lousy experience if any extensions are incompatible with the next update of gnome (which happened on every major update).
Trying to look at the source... Is the whole thing less than ~1000 LOC ???
The third buffer comes into play if you want to start working on the next frame _before_ the switch has occurred. So you start drawing in C, and if the right time should hit, the display system can still flip A and B. In this case, triple buffering gave you a head-start with drawing the frame in C.
Going further, if you complete the frame in C still before the A/B switch has happened, you queue up C as the next frame, instead of B. Then, you can start working on the next frame again in B. With this scheme, there is no sense in having more buffers than three.
Kudo's to Daniel van Vugt and all the testers that pitched in time and effort.
Does KDE/Plasma offer sthg. comparable?
KDE is way ahead in (almost) all departments these days.
Wishful thinking. I do 1st and 2nd level support on several hundred Linux desktops.
KDE isn't even close to Gnome when it comes to stability and Wayland support -- I mean: seriously? Wayland is a decade old.
And the last time I saw a stable KDE is two decades ago. I'm so annoyed by the crowd recommending it.
I'm tired of DrConqi leaving hundreds of useless systemd units behind and triggering countless alarms. Sucks, big time!
https://gitlab.gnome.org/GNOME/mutter/-/commits/48.rc?ref_ty...
So, unless they are disabled or backed out, seems they might land in Fedora 42?
