Summary: | [wayland] Adaptive Sync option sometimes disappears when waking from sleep | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Eamonn Rea <eamonnrea> |
Component: | platform-drm | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | nate, plasma-bugs, xaver.hugl |
Priority: | NOR | ||
Version First Reported In: | 6.1.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Eamonn Rea
2024-06-22 22:02:03 UTC
> Perhaps this is a driver issue when waking a laptop from sleep that is reporting to KDE that Adaptive Sync is unavailable? That is pretty likely; bug 486149 is similar and also about an internal display. Please check if the driver reports adaptive sync as supported even though KWin doesn't consider it supported. You can do that with drm_info. If you see > "vrr_capable" (immutable): range [0, 1] = 1 in its output after triggering the issue, it should be fixed by the same commit as bug 486149 Thanks, next time this occurs I will check for this. drm_info seems like exactly what i was looking for to check if this was a visual thing or if KWin is reflecting that the information has disappeared. I'm guessing that, if this is reproducible again and drm_info shows that VRR is not available, that this is a bug with DRM / some other part of the graphics stack and not KWin? This happened again today, although not when waking from sleep but on bootup after updating to Plasma 6.1.1. I have not rebooted since but I suspect rebooting will get the option to appear again. I installed `drm_info` from the AUR, and 9 connectors were returned. The first one, connector 0, does list VRR as being supported. The other ones, 1-8, list this as not being supported. Connector 0: - "vrr_capable" (immutable): range [0, 1] = 1 Connector 1-8: - "vrr_capable" (immutable): range [0, 1] = 0 okay, then it's definitely the same as bug 486149 *** This bug has been marked as a duplicate of bug 486149 *** |