SUMMARY Launching a fullscreen application in wayland when adaptive sync is set to "Enabled" or "Automatic" causes the application to render new frames only when you press something on the keyboard or do something with the mouse. Basically it makes games unplayable. Running the game in gamescope or windowed mode with adaptive sync works fine. STEPS TO REPRODUCE 1. Set adaptive sync to "Enabled" or "Automatic" 2. Select any game that can be run in fullscreen OBSERVED RESULT Frames are being generated only when doing something with mouse and keyboard. EXPECTED RESULT Should generate frames the same way as when adaptive sync is disabled SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ASUS TUF Gaming A16 FA617NS_FA617NS System Version: 1.0 ADDITIONAL INFORMATION Gpus reported by vulkaninfo Devices: ======== GPU0: apiVersion = 1.3.267 driverVersion = 23.3.1 vendorID = 0x1002 deviceID = 0x1681 deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU deviceName = AMD Radeon Graphics (RADV REMBRANDT) driverID = DRIVER_ID_MESA_RADV driverName = radv driverInfo = Mesa 23.3.1 conformanceVersion = 1.3.0.0 deviceUUID = 00000000-7700-0000-0000-000000000000 driverUUID = 414d442d-4d45-5341-2d44-525600000000 GPU1: apiVersion = 1.3.267 driverVersion = 23.3.1 vendorID = 0x1002 deviceID = 0x7480 deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = AMD Radeon RX 7600S (RADV NAVI33) driverID = DRIVER_ID_MESA_RADV driverName = radv driverInfo = Mesa 23.3.1 conformanceVersion = 1.3.0.0 deviceUUID = 00000000-0300-0000-0000-000000000000 driverUUID = 414d442d-4d45-5341-2d44-525600000000
With "automatic" option it is easier to reproduce the issue but it also happens with "Always". https://imgur.com/VLtoTtL
*** This bug has been marked as a duplicate of bug 479144 ***