Created attachment 181986 [details] Image of the odd cursor behavior, using a Monitor whit laptop. (using HDMI cable) the bug is not there on the laptop screen only on monitor. Bug: Brush paints a false/incorrect line when moving the cursor. KolourPaint: 25.04.1 KDE Frameworks: 6.13.0 Qt: Using 6.9.0 and built against 6.9.0 KDE Flatpak runtime (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.14.9-300.fc42.x86_64
Comment on attachment 181986 [details] Image of the odd cursor behavior, using a Monitor whit laptop. (using HDMI cable) the bug is not there on the laptop screen only on monitor. PC: Operating System: Fedora Linux 42 KDE Plasma Version: 6.3.91 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.9-300.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 6600H with Radeon Graphics Memory: 32 GiB of RAM (30.0 GiB usable) Graphics Processor 1: AMD Radeon 660M Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU Manufacturer: LENOVO System Version: Legion 5 15ARH7H
Hi - could you please check if you're using fractional display scaling (ex. 125%, 150%, etc.) on the monitor where you're seeing this issue? Thanks!
Bug Report: Fractional Scaling Issue at 125% Hey, Yes, I am using fractional scaling (125%) on my monitor. There are no issues when using fractional scaling at 100% and 150%; the problem only occurs at 125%. I also tried using fractional scaling (125%) on my laptop screen, and the same problem was present.
Thanks! And sorry, I forgot to also ask - does scrolling or resizing the window in some way, so that its contents are redrawn, cause those graphical artifacts to disappear?
hei, Graphical artifacts are visible only at 100% zoom. Artifacts disappear when resizing or moving the window. Artifacts disappear when zooming in or out from 100% zoom. Artifacts disappear when i move the mouse cursor to the color palette, but not if i move the mouse cursor to tool bar.
Thank you! That's enough to confirm that we're both experiencing the exact same issue, and I believe that this and one other bug report share the same root cause - merging those together to hopefully help with developer investigation :-) Thanks! *** This bug has been marked as a duplicate of bug 502103 ***