https://bugs.kde.org/show_bug.cgi?id=512591
Bug ID: 512591
Summary: Low application frame rate causes low cursor frame
rate when tearing is allowed
Classification: Plasma
Product: kwin
Version First unspecified
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 187158
--> https://bugs.kde.org/attachment.cgi?id=187158&action=edit
Video that demonstrates the issue
SUMMARY
When screen tearing is allowed in fullscreen and enabled for an app, the
cursor's frame rate appears to depend on the application's frame rate.
STEPS TO REPRODUCE
1. Enable "Screen tearing: Allow in fullscreen windows" in Display and Monitor
2. Force allow tearing for the application you are testing (for example through
Window Rules)
3. Fullscreen the application
OBSERVED RESULT
Lower application frame rates cause the cursor to also run at a lower frame
rate.
EXPECTED RESULT
The mouse cursor should be tied to the monitor's refresh rate, not the
application's frame rate.
SOFTWARE AND OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 x 12th Gen Intel Core i7-12700K
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060 Ti
Graphics Driver: nvidia-dkms 580.95.05-1 (proprietary)
ADDITIONAL INFORMATION
I am using a 240 Hz monitor, so this might not be noticeable at lower refresh
rates. I tried unplugging my 75 Hz second monitor, but this made no difference.
Enabling adaptive sync or disabling triple buffering does not change the
behavior.
See the video attached for a visual demonstration of this.
--
You are receiving this mail because:
You are watching all bug changes.
