- Triple buffering for GNOME 48:
- Finally reproduced the screen freeze from last week but it seems to already be fixed in the triple buffering branch for 48. I can’t yet figure out how much would need to be backported to 47 but it might not matter since the problem only seems to occur on newer kernels >= 6.12.
- Retested VRR in detail. It works but is still too broken to enable by default. That’s a bug on main, not in triple buffering.
- Retested multi-GPU-multi-monitor in detail. No problems found other than an Nvidia 560 showstopper in Ubuntu 25.04, but that’s not related to triple buffering and is already resolved by releasing Nvidia 570.
- Re-audited all the commits to ensure no rebase mistakes crept in.
- Researched amdgpu visual glitches to confirm they’re not specific to triple buffering.
- Fixed a screen freeze caused by a bad merge with the new Wayland ‘fifo’ and ‘commit-timing’ protocols in GNOME 48. The protocols themselves are only about 3 months old so only Wine 10.0’s new native Wayland driver was hitting the problem.
- All discussions were resolved for a few days, but then a new discussion was opened today.
- Spent more time debugging fullscreen direct scanout frame skips, not related to triple buffering but also not fixed by triple buffering. Now identified the two upstream latency optimizations causing the frame skips and working with upstream to fix them. A fix for one is already proposed.
- Migrated from IRC to Matrix.
- Lots of bug triage and user support in Launchpad and upstreams:
2 Likes