Bug 506530 - [AMD] Freesync flicker on desktop after exiting borderless window video game
Summary: [AMD] Freesync flicker on desktop after exiting borderless window video game
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: platform-drm (other bugs)
Version First Reported In: 6.4.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-03 13:16 UTC by zcastagna84
Modified: 2025-10-16 21:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zcastagna84 2025-07-03 13:16:33 UTC
SUMMARY
I am new to Linux, using the latest Bazzite OS. I’ve been playing final fantasy 16 with adaptive sync set to auto and the game running in borderless window. Consistently when i would close the game and return to desktop, the frame rates would be all over the place resulting in freesync flicker. Disabling and reenabling adaptive sync would stop. So far the “permanent “ fix is to run the game in exclusive fullscreen mode. As expected, when closing the game, the desktop refresh rate is pinned to 144hz rather than wildly fluctuating. 

STEPS TO REPRODUCE
1. Regularly playing the game in borderless window causes the issue upon closing
2. Disabling and enabling adaptive sync temporarily stops
3. 

OBSERVED RESULT
Extreme frame rate fluctuations and brightness flicker

EXPECTED RESULT
Stable frame rates on desktop with no brightness flicker 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Bazzite 42
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Graphics platform is Wayland. General system specs: 5700X3D, Asrock B350, 9070XT, 32Gbs RAM, MSI 1440p 144hz monitor connected with club 3D DisplayPort cable.
Comment 1 Zamundaaa 2025-10-16 21:52:40 UTC
This is a driver bug, see https://gitlab.freedesktop.org/drm/amd/-/issues/3546