https://bugs.kde.org/show_bug.cgi?id=469764
Bug ID: 469764 Summary: VRR Regression, signal lost on Wayland. Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: strelok.zer...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SETUP: Radeon + Nvidia hybrid graphics on Wayland. Radeon is the iGPU to which the monitor is connected, Nvidia is dGPU. I've tried it without Nvidia GPU enabled and the results are the same. STEPS TO REPRODUCE 1. Switch VRR setting to "always" 2. Instantly lose output signal Alternatively: 1. Switch VRR setting to "Automatic" 2. Lose signal only when full screen mode is enables. Happens when watching YouTube or something in VLC. OBSERVED RESULT Lost signal(Even the backlight of the screen is instantly off). After a few updates the screen turns on for a few seconds and then its off again. Especially if anything gets updated on the screen (cursor movement for example). EXPECTED RESULT Correct VRR operation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION The problem with that is that games on Wayland without VRR are unplayable, there is terrible stutter unless the game is rendered in FPS exceeding display capabilities. "Allow screen tearing to reduce the latency" option in compositor settings does not work, since there is no tearing regardless but the stuttering is present (possibly due to hybrid graphics). Marked this as a regression because on the same setup this wasn't the case a few releases ago. Unfortunately I cannot exactly remember when since, since I haven't tried playing games in a while. This happened back then as well but lowering Display refresh rate resolved the issue, it is no longer the case however. -- You are receiving this mail because: You are watching all bug changes.