https://bugs.kde.org/show_bug.cgi?id=514454
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC| |[email protected] --- Comment #1 from Zamundaaa <[email protected]> --- The reason for this could be that KWin sets HDR metadata each frame. With legacy modesetting, setting any properties may cause the driver to do a pageflip, so if we set the property + then another frame, the driver might end up pushing two frames instead of one. There are some workarounds we can consider, like splitting out the code path for "allow_modeset" in KWin to a separate function, but as no actual legacy drivers support HDR, maybe the best course of action would be to just remove the feature from legacy. Looking at drmdb.emersion.fr, the same applies to VRR as well. Why are you using legacy in the first place though? It's "legacy" for a reason, it's not supposed to be used unless your driver doesn't support the proper API. I've considered ripping out the env var to force it as well... -- You are receiving this mail because: You are watching all bug changes.
