animations that move the way they're supposed to
For nearly two years, a quiet technical compromise shaped the daily experience of countless Linux desktop users — Nvidia GPU owners running KDE Plasma watched their animations stutter, the visible cost of a synchronization bug that demanded a deliberate sacrifice. With the release of Plasma 6.7.3, the underlying fault has been repaired and triple buffering restored, a small but meaningful moment in the long, unglamorous work of maintaining the software environments we inhabit without thinking. It is a reminder that the smoothness we take for granted is always the product of someone, somewhere, solving a problem we never knew existed.
- Since October 2024, Nvidia users on KDE Plasma have endured stuttering animations — not from neglect, but from a deliberate workaround to a deeper synchronization bug in the KWin window manager.
- Double buffering, the fallback solution, introduced subtle visual hiccups that eroded the fluid desktop experience Plasma users expected, quietly degrading daily interactions for thousands.
- The KDE team traced the root cause to multi-GPU copy glitches, and only after confirming the fix was stable did they move to restore the original behavior — a disciplined, methodical path back.
- Plasma 6.7.3 is now available, carrying the single changelog line that matters most to affected users: triple buffering on Nvidia is allowed again, and the stuttering should be gone.
- Development momentum continues forward — Plasma 6.8 is already in progress, with new capabilities like audio-to-video recording in the Spectacle tool signaling that the team's attention has moved beyond the fix.
For nearly two years, KDE Plasma users running Nvidia graphics cards lived with a compromise they may not have fully understood. In October 2024, the KDE team made a deliberate decision to disable triple buffering across all Nvidia hardware — not out of carelessness, but because a synchronization bug in KWin, Plasma's window manager, was causing glitches when copying data between multiple GPUs. Disabling the feature was the responsible move. It was also a visible one.
Triple buffering smooths desktop animation by keeping three rendered frames in memory at once, ensuring a finished frame is always ready when the display needs it. Without it, the fallback is double buffering — functional, but prone to small visual gaps where the GPU outpaces the display. For Nvidia users, those gaps translated into stuttering animations and a desktop that felt slightly off, a low-grade friction that accumulated over time.
The resolution came without fanfare. The KDE team published Plasma 6.7.3, a routine maintenance release carrying two weeks of patches and refinements. Within its changelog, a single line announced what many had been waiting for: triple buffering on Nvidia was permitted again. The synchronization bug had been identified, fixed, and verified. There was nothing left blocking the feature's return.
What this moment illustrates is how desktop software actually improves — not through dramatic announcements, but through patient, incremental problem-solving that rarely surfaces until the work is done. For Nvidia users, the practical result is immediate: updating to Plasma 6.7.3 should restore the visual fluidity that triple buffering provides. The KDE team is already moving ahead, with Plasma 6.8 bringing new features to tools like Spectacle. But the quieter victory belongs to the users who will simply notice, one day soon, that their desktop feels smooth again.
For nearly two years, anyone running KDE Plasma on an Nvidia graphics card has been watching their desktop animations stutter. The culprit wasn't a mystery—it was a deliberate choice made in October 2024, when the KDE team disabled triple buffering across all Nvidia hardware. The reason was technical and specific: a synchronization bug in KWin, the window manager at Plasma's core, was causing glitches when copying data across multiple GPUs. It was a necessary sacrifice, the kind of trade-off that happens when you discover a problem you can't immediately solve.
Triple buffering is a rendering technique that smooths out animation by maintaining three frames in memory at once, allowing the system to always have a finished frame ready to display while the next one is being drawn. Without it, the system falls back to double buffering, which works but leaves small gaps—moments where the GPU finishes a frame before the display is ready to show it, creating the visual equivalent of a hiccup. For two years, Nvidia users on Plasma lived with that compromise.
The fix arrived quietly. On the KDE blog, the team announced the release of Plasma 6.7.3, a maintenance update bundling two weeks of patches, refinements, and translation updates. Buried in the changelog was a single line that would matter to thousands of users: "allow triple buffering on Nvidia again." The reason was straightforward. The synchronization bug that had forced the original disablement had been fixed. The multi-GPU copy glitches that plagued the system were gone. There were no remaining issues blocking its return.
The path to this moment reveals how desktop software development actually works—not as a series of dramatic breakthroughs, but as incremental problem-solving. Someone identified the root cause. Someone else fixed it. The fix was tested. Only then could the original feature be restored. It's unglamorous work, the kind that doesn't make headlines until you realize you've been living without something you didn't know you were missing.
For users who have been experiencing those stuttering animations, the fix is available now. Downloading Plasma 6.7.3 should restore the smoothness that triple buffering provides—the kind of visual fluidity that you notice most when it's absent, and barely notice when it's there. The KDE team is already looking ahead. Plasma 6.8, still in development, will bring new features like audio recording capabilities to the Spectacle screenshot tool. But for Nvidia users, the immediate win is simpler: animations that move the way they're supposed to.
Notable Quotes
It was disabled because of glitches with multi-GPU copies, which turned out to be a synchronization bug in KWin. Since the bug is fixed, and there don't seem to be any other issues anymore, we can enable it by default.— KDE development team (via commit explanation)
The Hearth Conversation Another angle on the story
Why did it take two years to fix this? Was it a hard problem?
Not hard in the way you might think—the issue was specific and reproducible. It was a synchronization bug in KWin affecting multi-GPU operations. The hard part was that they couldn't just patch it while leaving triple buffering enabled; the bug was too disruptive. So they disabled the feature and worked on the root cause.
And nobody complained?
Oh, people definitely complained. But the alternative was worse—leaving triple buffering on would have caused crashes and data corruption in multi-GPU setups. It was the right call, just not a popular one.
So this is just a bug fix, then? Nothing new?
Technically yes, but it matters. For Nvidia users, this restores performance they lost. Double buffering works, but it introduces frame timing issues that create visible stuttering. Triple buffering eliminates that. It's the difference between smooth and janky.
Will this affect AMD users or Intel users?
No—the bug was specific to how KWin handled Nvidia's multi-GPU architecture. AMD and Intel users either didn't have the issue or had workarounds. This fix is Nvidia-specific.
What's next for KDE?
They're moving forward with Plasma 6.8, which adds audio recording to their screenshot tool. But the real work is ongoing—maintaining stability, fixing edge cases, improving performance across different hardware configurations.