| Summary: | Refresh rate becomes unstable in Wayland using freesync at 4k 120hz only after using fullscreen windows | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | swim <swim> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | asubstanced, nate, streng.alexander, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.9 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
swim
2023-12-29 07:42:12 UTC
I forgot to mention, this issue does not occur at 4k120Hz in any configuration if I disable VRR/Freesync *** Bug 479222 has been marked as a duplicate of this bug. *** I have seen a similar issue to this when running KDE 6 - Beta 2 pulled from this COPR https://copr.fedorainfracloud.org/coprs/solopasha/kde6/ into my Fedora 39 system running Nvidia. I additionally have explicit sync patches applied for Xwayland and Wayland-protos as provided from the Nobara Project COPR. I do not actually have this problem with KDE 5.27.10 (evertything else the same) only when switching to KDE 6 - Beta 2 as noted above. I haven't reported it as my setup was obviously not setup in an ideal fashion for testing. However I mention it as I have a similar setup with similar results when using Beta 2 in case it helps triangulate the issue. It might be revealing that it doesn't happen to me as an Nvidia user in 5.27.10 but does in 6 beta 2. I tried enabling disabling other settings and these did not affect the issue. To note VRR does not enable as I run the DP to HDMI adapater due to bandwidth limitations on the HDMI port. Issue: "When using a display port to hdmi adapter there is also a blank screen/black screen effect." For me the issue is actually only this element, but consistently if I have the resolution at 3840x1600 and 120hz. It mostly occurs when opening a new application, or opening the start bar. If I watch a video or do anything in an already open window I don't have an issue. Also games will run totally fine. Hardware: Nvidia 2080 Samsung QN90B set at ultrawide 3840x1600 - DP to HDMI 2.1 converter Denon AVR-2500HX - HDMI for sound SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 6.6.0.5-amd64 (available in About System) KDE Plasma Version: 5.91.0 KDE Frameworks Version: Did not check before reverting Qt Version: Did not check before reverting Can you still reproduce this on Plasma 6? If so, please attach the output of drm_info before, and after triggering the issue For me this issue is now resolved. In my case I still have issues with freesync in Fedora 40 KDE Plasma 6.0.3 . I Tested freesync in Doom Eternal and in fight scenarios the fps would tank very badly if I had adaptive sync in either "automatic" or "always" mode. I have an Asus Tuf a16 advantage edition (2023) laptop which has a freesync display built-in. (In reply to Alexander Streng from comment #6) > In my case I still have issues with freesync in Fedora 40 KDE Plasma 6.0.3 . > I Tested freesync in Doom Eternal and in fight scenarios the fps would tank > very badly if I had adaptive sync in either "automatic" or "always" mode. > > I have an Asus Tuf a16 advantage edition (2023) laptop which has a freesync > display built-in. Okay, that sounds like an unrelated issue; please make a new bug report for it (In reply to Zamundaaa from comment #4) > Can you still reproduce this on Plasma 6? If so, please attach the output of > drm_info before, and after triggering the issue I do not have this problem as I originally described it in kde 6. freesync does work with hdmi on full screen videos and games. However, I am encountering the same resulting effect when waking the computer from sleep. At the login screen, the screen will flicker with freesync enabled or disabled only when I turn my monitor on and wake the pc(or wake up pc, turn monitor on). I cannot stop this without setting the refresh rate to 60 and then back to 120hz. I have not delved into it fully and assume its a separate issue. The only commonality between this report and my new problem is that this occurs only on 120hz refresh rate. Its almost like kde and the graphics card lock to an incorrect refresh rate right when the pc wakes up. Like the display has not had enough time to stabilize to 120hz before kde syncs to the output. This also does not happen when booting, which leads me to believe its something to do with kde. As I said I have not had much time to look into it to make a formal bug report. |