https://bugs.documentfoundation.org/show_bug.cgi?id=152911
--- Comment #103 from Gauthier <[email protected]> --- What Michael says is true, however it should be acknowledge that the issue reported here is not an edge case, but the default behaviour on Wayland, and as such must be addressed sooner rather than later given most distros now ship wayland by default. I've redone some test using two different machine. One with AMD Radeon iGPU: Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.9-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 6650U with Radeon Graphics Memory: 32 GiB of RAM (30.7 GiB usable) Graphics Processor: AMD Radeon Graphics Another with Intel UHD Graphic 620. Operating System: Fedora Linux 43 beta KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.17 Graphics Platform: Wayland Processors: 8 × Intel i5-8350U Memory: 16 GiB of RAM Graphics Processor: Intel UHD Graphic 620 Both laptop have a 1080p 14" screen. There is a noticeable lag during scrolling with both the kf6 and gtk3 VCL back-ends and this on both machines (more details below). There is no lag when using the xcb backend. Influencing factors: ==================== - VCL back-ends: the lag is significantly worse using the kf6 over the gtk3 back-end - Screens: the lag significantly worsen when plugin in an external screen I'd say that for any Qt/Kf based distro, this make the lag behaviour basically a default, and while usable in case of using a single, reasonably low res, screen, it becomes unusable as soon as using another screen. -- You are receiving this mail because: You are the assignee for the bug.
